Webpacker: Publish new release

[JoshRobertson]

@gauravtiwari there are a few useful changes sitting in master since August (including the move away node-sass), could we please cut a new NPM release?

Thanks!

[gauravtiwari]

thanks for nudging @JoshRobertson

Yes, I am keen on getting a release out too but there are a few major breaking changes, which I am thinking to ship as one big 6.0 release including support for Webpack 5 (blocker: https://github.com/webdeveric/webpack-assets-manifest/issues/95)

[rossta]

@gauravtiwari Any way to preview what you have in mind for the 6.0 release or contribute help (beta testing, docs, feature development)? Thanks!

[mrhead]

@gauravtiwari Would it be possible to update the @next tag? At the moment, yarn add @rails/webpacker@next suggested by README installs version 4.0.0-rc.

[aried3r]

there are a few major breaking changes

Should we maybe begin writing these down in the changelog? Especially in case people need to change their configs to migrate. In case you identified some, I'd be happy to try to whip up some entries for these.

[patsplat]

I'm particularly interested in back-porting the node-sass deprecation to the 5.x.x branch, but am unsure of how to help in a productive manner.

If there is anything I can do to help support a release please let me know.

[shaicoleman]

Yes, I am keen on getting a release out too but there are a few major breaking changes, which I am thinking to ship as one big 6.0 release including support for Webpack 5 (blocker: webdeveric/webpack-assets-manifest#95)

@gauravtiwari , FYI, that issue has been fixed