Added support for configuring the exclude rule of the webpack config #13
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
Added section in Readme about transpiling packages in node_modules
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.
I've been struggling for days to get Next JS to play nice with untranspiled Linaria files in a component library that we're building, until I finally came across this discussion in the Linaria repo callstack/linaria#178 (comment)
The last missing piece here, then, is being able to configure the exclude of the linaria webpack rule. Since Linaria has it's own array of rules, I thought this approach could be useful for allowing to override both in one go.
I've tested it with https://github.com/martpie/next-transpile-modules, which works just fine!
Let me know what you think!