Potential build error
See original GitHub issueWhen trying to build this project, I get the below error:
npm install -g vue
npm install vue-select
cd node-modules/vue-select
npm install
npm run build
ERROR in vue-select.js from UglifyJs
SyntaxError: Unexpected token: name (VueSelect) [./src/index.js:1,0]
This makes me think that vue isn’t installed correctly, but I have tried various ways of installing it via npm (installing it globally, installing it as a dependency instead of a peer dependency, installing it locally).
I wouldn’t be surprised if this was being caused by something I was doing wrong, I’m new to js/npm/webpack. Any help would be greatly appreciated.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
SyntaxError: The requested module 'react' does not provide an ...
I get this error when trying to build for production a previously working deployment after npm update. Does anyone have any ideas? `...
Read more >Xcode boilerplate openGL build pro… - Apple Developer
Xcode boilerplate openGL build produces error: "error finding potential wrapper bundle for node <FSNode 0x100a09910>".
Read more >`error finding potential wrapper bundle for node <>` - Stack ...
I am working on compiling a simple openGL program in Xcode on my M1 Mac. When I build, It succeeds, but I get...
Read more >Common Build Problems - Travis CI Docs
A very common cause when a test is suddenly breaking without any major code changes involved is a change in upstream dependencies. This...
Read more >ui: fix potential compile error. - public-inbox listing
ui: fix potential compile error. @ 2020-09-02 3:04 ruippan(潘睿) 2020-09-02 5:23 ` kraxel 0 siblings, 1 reply; 4+ messages in thread From: ruippan(潘睿) ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hello,
I forking & cloning, but stumbled upon the same problem:
How can I solve it? Many thanks
That worked for me! It’s a matter of cloning the repo vs installing it via npm. Thanks!