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

Having issues when running "source ../env.sh; webpack --watch --progress" #60

Closed
gillytron opened this issue Jan 16, 2019 · 2 comments
Closed

Comments

@gillytron
Copy link

when executing source ../env.sh; webpack --watch --progress
I get the following output:

One CLI for webpack must be installed. These are recommended choices, delivered as separate packages:
 - webpack-cli (https://github.com/webpack/webpack-cli)
   The original webpack full-featured CLI.
We will use "yarn" to install the CLI via "yarn add -D".
Do you want to install 'webpack-cli' (yes/no): yarn add -D

I then run 'yarn add -D webpack-cli'

Installing 'webpack-cli' (running 'yarn add -D webpack-cli')...
yarn add v1.13.0
warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.
[1/5] 🔍  Validating package.json...
error app@1.0.0: The engine "node" is incompatible with this module. Expected version "9.x". Got "11.6.0"
error Found incompatible module
info Visit https://yarnpkg.com/en/docs/cli/add for documentation about this command.
undefined

however, there's seems to be some package incompatibilities with node. Can please some advise on how to overcome this issue?

thanks

@vincentroman
Copy link

run npm install webpack@3.11.0 with sudo permission or run sudo apt install webpack in the app directory

@roryscot
Copy link

@BishopMildert This is a simple indication that you have a package-lock.json, which means you have npm installed as a package manager in addition to yarn (which uses yarn.lock). This is not an issue with stream-react-example as far as I can tell.

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

3 participants