Closed brad-larson closed 5 years ago
Bummer, unable to reproduce on my machine. Wondering if it's an environmental thing and if so, what the difference is.
We're running the same node version. Maybe it's a yarn version thing?
$ nvm current
v8.10.0
$ yarn --version
1.9.4
$
Hmm, my yarn version is also 1.9.4
No such file or directory - /Users/brad/src/api/node_modules/.bin/webpack
,
If my app's root directory is /Users/brad/src/api
, should there be a node_modules
directory there?
I do not have one, and cannot find a package.json
within the project directory.
@brad-larson
RE: should there be a node_modules directory there? I do not have one, and cannot find a package.json within the project directory.
Yup, both package.json
and node_modules
should exist.
This might provide some debugging help. The jets new
command calls jets webpacker:install
as part of the process. In turn, that ultimately runs this template script: https://github.com/tongueroo/webpacker/blob/master/lib/install/template.rb
That creates the package.json
and node_modules
. So something funny where it's not creating those files. Thinking maybe try running a yarn install
command directly to see if that reveals more information. Something like:
yarn add @rails/webpacker coffeescript@1.12.7
This also reminds me of #187 He had some issues and he ended up removing his node related folders in his home directory. That cleared out the issue. Think this may be environment specific, unfortunately.
Gotcha, thanks for the help
Checklist
jets upgrade
command that makes this a simple task. There's also an Upgrading Guide: http://rubyonjets.com/docs/upgrading/My Environment
Expected Behaviour
I expect the following to not error:
I also expect the following to work:
Current Behavior
It fails:
So does this:
Solution Suggestion
It seems like there is an issue with the webpacker configuration.