chore: improve Stackblitz publishing flow #203
Merged
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.
Description
RE: #125
Right now, I have to manually update our Stackblitz template in my personal template at https://hydrogen.new whenever we ship a release. This does not scale.
This PR:
_gitignore
so it gets picked up properly by stackblitz and force pushes to thestackblitz
branchLOCAL_DEV
to prefix thedev-server
script in the root of the monorepoYou can test out this new flow: https://stackblitz.com/fork/github/shopify/hydrogen/tree/stackblitz/packages/dev
Additional context
The
gitignore
shenanigans are to work around an interesting NPM publish behavior which renames.gitignore
to.npmignore
lolol npm/npm#1862Before submitting the PR, please make sure you do the following:
fixes #123
)