Merged
Conversation
Contributor
|
@parrt blessed |
|
I am having the same issue, any idea when we might expect an updated npm package with the merged changes? |
Member
|
We are actually doing quite a number of important changes so I don't have a date for you but I'm hoping within a month or so we can get 4.10 out the door. |
|
Any news for this to be added in a release? |
Member
|
Finally got in major changes that I needed to make so I will start the release process over the next weak or two. sorry for the delay. This has been merged so it will show up in the release 4.10 |
Member
|
(It's in dev branch now if you'd like to try out) |
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
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.
This is an attempt to fix runtime browser issue - #2852 for environments like create-react-app where there is no possibility to manipulate webpack config without ejecting the application. I did this locally for installed antlr4 package and it helped me. Hope this solution is good enough.
Please also read webpack 5 migration notes :
Package authors: Use the browser field in package.json to make a package frontend-compatible. Provide alternative implementations/dependencies for the browser.
Ignore module in package.json
Thank you for the great tool!