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

elm.js at top level causes problems with VSCode on Windows #9

Closed
melston opened this issue Mar 4, 2020 · 3 comments
Closed

elm.js at top level causes problems with VSCode on Windows #9

melston opened this issue Mar 4, 2020 · 3 comments

Comments

@melston
Copy link

melston commented Mar 4, 2020

When using VSCode with the elm tooling extension on Windows the presence of the elm.js file at the top level of the project causes a popup every time you open one of the elm files in the src directory. It complains that "'console' is undefined".

The recommendation (taken from an elm-tooling issue ) is to not name the bundle 'elm.js'.

@rtfeldman
Copy link
Owner

Thanks! This has already been fixed in the final draft of the book (it uses app.js throughout now) but I haven't circled back and updated this repo yet. 😄

@melston
Copy link
Author

melston commented Mar 6, 2020

In the meantime I took a slightly different approach (which seems to work). I use 'elm.js' but put it in a 'js' subdirectory. VSCode is fine with that and I don't see any other issues. I did update the index.html file accordingly.

@melston melston closed this as completed Mar 6, 2020
@razzeee
Copy link

razzeee commented Mar 26, 2020

To add some more info, it's not due to VSCode, but how your shell handles file endings in windows.

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