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

'npm run build' ERROR in chunk vendor when using node 6.x #93

Closed
kuncevic opened this issue May 10, 2016 · 10 comments
Closed

'npm run build' ERROR in chunk vendor when using node 6.x #93

kuncevic opened this issue May 10, 2016 · 10 comments

Comments

@kuncevic
Copy link

kuncevic commented May 10, 2016

getting error when running npm run build

ERROR in chunk vendor [initial]
js/[name].[hash].js
No template for dependency: TemplateArgumentDependency
Child html-webpack-plugin for "index.html":
        + 1 hidden modules
Child extract-text-webpack-plugin:
        + 2 hidden modules
@Foxandxss
Copy link
Member

Uh, weird. I will try with a fresh build.

@Foxandxss
Copy link
Member

What node & npm are you using? Works for me.

@kuncevic
Copy link
Author

Node 6.1 NPM 3.8.6 I will check with node 5 and 4 now.

@kuncevic
Copy link
Author

So I just double check with a fresh project and yes there is an exact issue I described above when using node 6.1

Node 5.8 and npm 3.8.5 - OK
Node 4.4.0 and npm 3.8.2 - OK

Also FYI I am on Win 10.

@Foxandxss
Copy link
Member

I heard that node 6.x is giving issues, but I will check.

@kuncevic kuncevic changed the title 'npm run build' ERROR in chunk vendor 'npm run build' ERROR in chunk vendor when using node 6.x May 10, 2016
@ncrawlins
Copy link

this happened for me, because I changed the nodevars.bat to load node and start in "c:/work".

If I changed that to to "C:/work" it builds fine. Apparently node 6 is treating C:\foo and c:\foo as different places or something. so you have to be careful if you're ever explicitly using windows drive letter somewhere

nodejs/node#6624

@matsprea
Copy link

matsprea commented Jun 7, 2016

I had this issue with Node 6.1, but the upgrade to Node 6.2.1 solved it.
Hope this helps.

@alexbet
Copy link

alexbet commented Aug 18, 2016

I have Node 6.4.0 and have this issue. Was anyone able to resolve it?

@michaeljota
Copy link

michaeljota commented Sep 18, 2016

I'm not using this project, but this. However, I'm getting this same issue. How do you guys solve it?

@kuncevic
Copy link
Author

kuncevic commented Nov 5, 2016

@michaeljota just do not use node 6.1 use https://github.com/creationix/nvm to switch to another verson.

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

6 participants