-
Notifications
You must be signed in to change notification settings - Fork 1
Feature/package improvements #96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Abe <[email protected]>
Signed-off-by: Abe <[email protected]>
Signed-off-by: Abe <[email protected]>
Signed-off-by: Abe <[email protected]>
Signed-off-by: Abe <[email protected]>
Signed-off-by: Abe <[email protected]>
Signed-off-by: Abe <[email protected]>
Signed-off-by: Abe <[email protected]>
Signed-off-by: Abe <[email protected]>
…rs. (#74) * chore: Rename ROUTES to ONEFE_ROUTES and update imports throughout * feat: export ONEFE_ROUTES for use in starter app service worker * feat: introducing onBeforeRender hook to initialize service workers. * chore: moving to non-deprecated react-dom API * fix: fix playwright install steps in workflow * Update pr-e2e-test-check.yml * fix: fix playwright install issues in workflows and remove it where not necessary * fix: [workflow] updated yarn playwright version query
…r, and cli to npm (#75)
references in published packages.
* Update action.yml * feat: removing self ssh key because its not needed anymore.
* Adding check for node version * Removing node 22 version. * Adding an action to see if that helps solve the issue of authenticating with npm to get the pipeline to succeed. * adding changeset. * Moving the authenticate to npm step a bit before. * Removing the step which would have deployed the web app through 1fe mono-repo. We don't need to do that anymore. * Vibe coded a README file. * Updating the READme to be clean and concise. * Ensuring right order of steps in the CI-CD pipeline. * Adding a step to authenticate to npm so submodules package download will work. * Adding an environment variable so we are able to authenticate with npm. * Updating the READme.md for create-1fe-app package. * Removing file which isn't needed and also updating READMe file for create-1fe-app package. * Removing un-necessary file.
* Don't need to deploy to azure web app from this repo anymore. * Attempt to fix package publishing to npm private org. * Removing un-needed param.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Updating all packages to now reference playground instead of bathtub when working with such. * Adding a changeset.
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: cvarma2 <[email protected]>
… start here and fix ci (#90)
Signed-off-by: cvarma2 <[email protected]>
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
* Add changeset for patch bump of all packages * Remove typescript-config and eslint-config from changeset
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
…kages - Add local 1FE logo SVG to each package assets folder - Add professional badges (npm version, MIT license, community) - Add SEO keywords for npm discoverability - Add descriptive package descriptions - Fix badge links to point to npm package pages - Create changeset for patch version bumps - Update documentation links and add community sections
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.