-
-
Notifications
You must be signed in to change notification settings - Fork 33.7k
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
Unable to build Vue on Windows using npm/yarn run build #4338
Comments
Seems to be a bug of |
Closing since the source of the issue is in a dependency, and is not a bug in the framework itself. |
I'm trying to file a PR for Vue, but I cannot get it to build - is there any recommendation on how to move forward? |
11 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Versions
Vue.js = 2.0.2
Node.js = 6.9.1
NPM = 4.0.2
Windows 10
Steps to reproduce
or
What is Expected?
The expected behavior is that all versions of vue are build in the dist folder.
What is actually happening?
Error: Could not load C:\Development\github\vue\src\core/index (imported by C:\Development\github\vue\src\entries\web-runtime.js): ENOENT: no such file or directory, open 'C:\Development\github\vue\src\core\index'
at C:\Development\github\vue\node_modules\rollup\dist\rollup.js:8833:10
at process._tickCallback (internal/process/next_tick.js:103:7)
at Module.runMain (module.js:606:11)
at run (bootstrap_node.js:394:7)
at startup (bootstrap_node.js:149:9)
at bootstrap_node.js:509:3
Workaround
It appears that all imports that use the aliases defined in build/alias.js file do not work when the extension .js is not used. When .js is added to all imports, the build succeeds.
The text was updated successfully, but these errors were encountered: