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

Unable to build Vue on Windows using npm/yarn run build #4338

Closed
remcohuijser opened this issue Nov 29, 2016 · 3 comments
Closed

Unable to build Vue on Windows using npm/yarn run build #4338

remcohuijser opened this issue Nov 29, 2016 · 3 comments

Comments

@remcohuijser
Copy link

Versions

Vue.js = 2.0.2
Node.js = 6.9.1
NPM = 4.0.2
Windows 10

Steps to reproduce

  • Clone repo from GitHub
  • npm install
  • npm run build

or

  • Clone repo from GitHub
  • yarn install
  • yarn run build

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.

@defcc
Copy link
Member

defcc commented Nov 30, 2016

Seems to be a bug of rollup-plugin-alias. rollup/rollup-plugin-alias#11

@yyx990803
Copy link
Member

Closing since the source of the issue is in a dependency, and is not a bug in the framework itself.

@fenduru
Copy link
Contributor

fenduru commented Aug 4, 2017

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?

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

4 participants