-
-
Notifications
You must be signed in to change notification settings - Fork 375
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
Couldn't find preset "es2015" relative to directory #9
Comments
Might be a file path issue on Windows. I'll try to track it down. |
Similar error for me on OSX
|
Hmm - what version of npm? |
npm: 3.10.9 |
Darn, was sure it would be npm 2 haha. |
That was my bet too. 😞 |
No matter how deep in the directory structure the project is created babel is always looking for the es2015 preset in the users directory.
|
Removing |
oooh - i had forgotten it does resolution like that. maybe @hzoo knows |
I can confirm this on Ubuntu
This only happens with package has |
@thangngoc89 do you have a file at |
@developit No. I didn't make any custom settings to the project (yet), everything is standard Preact components |
@thangngoc89 You may created the |
@maoberlehner Still no. ❯ cat ~/.babelrc Any idea? |
very odd. I had thought we'd narrowed it down. One other thought: a |
@developit I though about that too and still no. I'll try to make a reproduce when I get back |
Just to confirm: @thangngoc89 what's your Node version? |
In Windows 10 I solved the issue by removing a .babelrc file in a parent directory. Thanks |
It happens on npm@4 too, I just got so excited with npm@5 . @developit So I traced down the problem, I only encounter it when the module was published with
Remove |
Ohhh, cool! Thanks for the versions and for tracing this! This has to be related to our custom module resolution function, and likely a combination of a missing babel option. I'm not at my desk right now but I'll give it a look later. |
@lukeed For now, I added this to preinstall in package.json |
Haha I'll definitely try! Is there a dead simple reproduction I can use? It looks like I can just install |
@lukeed yessss. Here:
|
Perfect, thank you. I'll get on this. |
I tracked down the issue. 🎉 Will open a PR tomorrow. In the meantime @thangngoc89, you can just |
I'm getting an error with a newly created app. I'm just trying to run it after the initial install.
Navigating to
localhost:8080
I get a 404.The text was updated successfully, but these errors were encountered: