Parcel: Not working when trying "Getting started" example

Created on 21 Dec 2017  路  3Comments  路  Source: parcel-bundler/parcel

Choose one: 馃悰 bug report

馃帥 Configuration (.babelrc, package.json, cli command)

No config.

馃 Expected Behavior

It compiles JS/TS and serves the page.

馃槸 Current Behavior

> parcel index.html
(node:17920) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): Error: EACCES: permission denied, open '/usr/local/share/.config/yarn/global/node_modules/anymatch/node_modules/array-unique/index.js'
(node:17920) DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
>

After error message it exits.

馃實 Your Environment

| Software | Version(s) |
| ---------------- | ---------- |
| Parcel | 1.2.1
| Node | 7.7.3
| Yarn | 0.17.3
| Operating System | Kubuntu 16.04 LTS

Most helpful comment

Tried removing anymatch from that directory (didn't want to lose other globally installed packages) and reinstalling parcel, it didn't help.

Uninstalled it from yarn and installed it via npm and now it works 馃槃, thanks. Not sure what is wrong with my yarn thought 馃槖.

All 3 comments

Sounds like yarn has made a hash of your global modules. I'm pretty sure this isn't a parceljs bug.

I'd be tempted to blow away '/usr/local/share/.config/yarn/global/node_modules and try again.

Tried removing anymatch from that directory (didn't want to lose other globally installed packages) and reinstalling parcel, it didn't help.

Uninstalled it from yarn and installed it via npm and now it works 馃槃, thanks. Not sure what is wrong with my yarn thought 馃槖.

I'm having the same problem, just did a global install on macOS using npm (I installed the latest version of Node prior). I hit parcel index.html in the terminal and nothing happens. None of the switches work.

EDIT
Right - I've answered my own problem ignore. Even though I installed Node I had nvm installed and it was using a pretty old version! Worth noting though as I'd not had any npm issues prior (I was using version 5).

Was this page helpful?
0 / 5 - 0 ratings