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.
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
Make the SDK friendly to locally link and develop on #693
Make the SDK friendly to locally link and develop on #693
Changes from 7 commits
cd007b4
8fb2b27
0023ab3
d247bc4
95d1730
dd06d78
2401b7f
12d6447
f61bf60
f56dc58
e9cee2e
f1e07b6
ce289ba
d053d43
75098b4
e54482e
639358b
b725269
1b2a6b5
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Referencing
hydrogen.es.js
directly in the build,./lib-build/hydrogen.es.js
, to make it compatible with watching for an local changes and rebuild:yarn run vite build -c vite.sdk-lib-config.js --watch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This export isn't used but it's part of the
./scripts/sdk/transform-paths.js ./src/platform/web/sdk/paths/vite.js ./target/paths/vite.js
stuff inbuild.sh
that's currently commented out.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fix #682
Make the assets path available to reference and serve separately.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Only remove the directory contents instead of the whole directory to maintain the
npm link
/yarn link
symlinkThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added as a comment to the script
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of needing to move these 3 files and rename them without the hash here, we handle removing the hash in
vite.sdk-assets-config.js
(rollupOptions.output.assetFileNames
) and reference them directly in place in thepackage.json
exports
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Instead of renaming these files in
build.sh
, we can just give them the proper name as part of the Vite build.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For reference, docs for the
rollupOptions.output.assetFileNames
option, https://rollupjs.org/guide/en/#outputassetfilenames