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

<% if (webpackConfig.htmlElements.headTags) etc #762

Closed
alvipeo opened this issue Jul 7, 2016 · 3 comments
Closed

<% if (webpackConfig.htmlElements.headTags) etc #762

alvipeo opened this issue Jul 7, 2016 · 3 comments

Comments

@alvipeo
Copy link

alvipeo commented Jul 7, 2016

Hi,

haven't looked at this repo for a while. Just cloned it and run, got this:

<% if (webpackConfig.htmlElements.headTags) { %> <%= webpackConfig.htmlElements.headTags %> <% } %>

on the top, and this:

<% if (webpackConfig.metadata.isDevServer) { %> <% } %>

at the bottom.

Node 6.1.3

@alvipeo
Copy link
Author

alvipeo commented Jul 11, 2016

Just checked yesterday, these artifacts disappeared. Closing.

@alvipeo alvipeo closed this as completed Jul 11, 2016
@supermarcos
Copy link

I know it is closed already but I will put my discover that, believe it or not (I still can hardly believe it), if you are on a Windows machine the problem is how you get to the path where your app is... I will explain myself:
If you have in D:\Projects\project_whatever your project and you go cd d:, then cd project... and so on, that will break webpack, but if you go cd D: then cd Project it will work!
Webpack will break if you don't follow exactly the same case. As simple and stupid as that...
Hopefully this helps somebody with the same problem in the future.

@tedvanderveen
Copy link

tedvanderveen commented Sep 9, 2016

I believe this is related: microsoft/vscode#9448

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

3 participants