Skip to content
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 2 configuration #99

Closed
agpt opened this issue Apr 10, 2017 · 4 comments
Closed

webpack 2 configuration #99

agpt opened this issue Apr 10, 2017 · 4 comments

Comments

@agpt
Copy link

agpt commented Apr 10, 2017

I believe webpack 2 now has slightly different syntax than what we had in webpack 1. e.g. module.loaders are now module.rules.

Ref. https://webpack.js.org/guides/migrating/#module-loaders-is-now-module-rules

@jeantoledo
Copy link

jeantoledo commented Apr 10, 2017

Can I get this issue? I've worked a lot with Webpack 2 in the last weeks!

@jeremy-brooks
Copy link

jeremy-brooks commented Apr 2, 2019

Is this related to the error that I am getting when running npm run webpack where it is complaining about the monaco-editor module saying Module parse failed and it was specifically at the getModule method?

FYI
Running: windows 10, npm in powershell with the latest version of npm and webpack 2.

@Marc-Dalmau
Copy link

Hi, I have exactly the same issue that @jeremy-brooks.

I'm using Mac OS X, and last version of npm and webpack 2.

@EP36 EP36 closed this as completed Aug 10, 2019
@EP36
Copy link
Collaborator

EP36 commented Aug 10, 2019

We have made a universal config for 3.0. Check it out! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants