Upgrading to 1.1 breaks

[MatthiasRMS]

After running bundle update (and noticing that I went from 1.0 to 1.1), relaunching my server (locally), I have this error:
Can't find application.js in /my_app/public/packs/manifest.json. Is webpack still compiling?

When specifying 1.0 in my gemfile, it works fine. When moving back to 1.1, error comes back.

I have a basic setup, similar to what you advise in the readme.
Happy to invite one of the maintainer to our private repo.

[gauravtiwari]

@MatthiasRMS You would need to re-run bundle exec rails webpacker:install and bundle exec rails webpacker:install:{react, angular, vue} if you have added these too.

[BoleLee]

I also met this error:
Can't find application.js in /my_app/public/packs/manifest.json. Is webpack still compiling?

ubuntu 16.04
rails: 5.0.2
the main step that I take:

Gemfile: 
gem 'webpacker', github: 'rails/webpacker'

bundle install
rails webpacker:install && rails webpacker:install:vue

when I add <%= javascript_pack_tag 'application' %>, it went this error.

Besides, I already install yarn, which version is 0.22, however, when I run rails webpacker:install && rails webpacker:install:vue, it comes with some messages:

Yarn executable was not detected in the system.
Download Yarn at https://yarnpkg.com/en/docs/install

[gauravtiwari]

@BoleLee Is yarn available in the path? Can you verify please if yarn --version runs okay?

[metaskills]

New to Yarn and such, but I noticed the latest 0.22 of Yarn uses the yarn bin name which is installed and in my path. But I noticed the ./bin/yarn stub wants to call yarnpkg seen here: https://github.com/rails/webpacker/blob/master/lib/install/bin/yarn.tt#L5

I have no such binary called yarnpkg. Did things change?

[inchr]

I've the same problem.

I've checked the prerequisites and are all ok. Any idea ? (it's a new app, so it's not an upgrade)

[inchr]

@gauravtiwari it says:
yarn --version
0.21.3

[ytbryan]

yarnpkg and yarn refer to the same thing.
Update: ok, not exactly the same, but yarn ships with yarnpkg. See https://github.com/yarnpkg/yarn/tree/master/bin cc @metaskills

If you have already have yarn installed, I would check if your webpack-dev-server port is free. At development.server.yml, try to change it from the default 8080 to something else.

[metaskills]

Is yarnpkg installed for everyone? It was certainly not installed for me.

[gauravtiwari]

@metaskills How did you install yarn - homebrew or npm? https://yarnpkg.com/lang/en/docs/install/ I have installed with homebrew and both binaries are available.

[metaskills]

How did you install yarn - homebrew or npm

Neither.... MacPorts.

[gauravtiwari]

Hmm, then I guess it's something to do with MacPorts 😄

[metaskills]

Honestly tho... what is the primary binary name? Is one an alias for the other? Are they different?

[inchr]

I used homebrew...btw now seems to be ok after I've started again the webpack server in development.

[ytbryan]

anyway, Gaurav changed yarnpkg to yarn in this PR https://github.com/rails/webpacker/pull/264/files#diff-d4fa2613404db474328053641eaae683