-
Notifications
You must be signed in to change notification settings - Fork 14
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
Webpack 4 support #31
Conversation
…or..of loop over the modulesIterable object
…ent so that webpack doesn't do aggressive tree-shaking and strip out the module import
of an exclude option. I want to exclude node_modules paths from getting prettified.
Hey, thanks for your great work on this! 👏 I see you started a bit of work toward #19 as well; I'd like to keep these efforts separate for now, but I'd love another PR for that so we could back-port it to a webpack < 4 compatible release if you're interested to help out there too! 😄 Current thoughts are:
That said, is there anything else left for Webpack 4 support outstanding with this PR? |
I don't think there's anything outstanding for webpack 4 support. I removed the #19 work-in-progress prior to creating this PR, so I think it's ready to go! |
Closing for #32 |
fixes #31
Upgrade dependencies and support the webpack 4 plugin system. Didn't make any attempt to support earlier versions of webpack (maybe should add webpack ^4.0.0 as a peer dependency?).
Needed to tweak the tests to get them to pass, and needed to update the jest configuration slightly.