262 Remove asset build from release, update entrypoint #267
+3
−2
Conversation
This file contains 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
tomjn
approved these changes
Mar 13, 2024
mattheu
reviewed
Mar 13, 2024
There was a problem hiding this comment.
I think if you're removing the build from releases, why not remove the build process completely. I think that not having to support that as part of the main project would be a big benefit to this.
I'm keen to know whether you've tested this. Does it work OK in your project like this? I guess we could release a 0.7.0 alpha version and try it out?
mattheu
requested changes
Nov 19, 2024
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.
Resolves #262
Remove the build assets from npm releases, and update the
mainfield in package.json to keep imports working the same.