Skip to content
This repository has been archived by the owner on Feb 24, 2024. It is now read-only.

Moving to use Webpack 4 #1007

Merged
merged 8 commits into from
Apr 6, 2018
Merged

Moving to use Webpack 4 #1007

merged 8 commits into from
Apr 6, 2018

Conversation

paganotoni
Copy link
Member

@paganotoni paganotoni commented Apr 5, 2018

This PR moves new buffalo templates to use webpack 4.5 it also attempts to organize the JS code in generated webpack.config.js.

Props on this one to @stanislas-m for all the help and guidance!

],
}

Glob.sync("./assets/*/*.*").reduce((_, entry) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you use reduce here, you'll drop the first file, even if it's not application.scss. :)

@paganotoni paganotoni changed the title WIP: Moving to use Webpack 4 Moving to use Webpack 4 Apr 5, 2018
@paganotoni
Copy link
Member Author

@stanislas-m all set with that change.

@markbates markbates merged commit 59b4005 into development Apr 6, 2018
@markbates markbates deleted the feature/moving-to-webpack-4 branch April 6, 2018 18:54
@markbates markbates added this to the 0.11.1 milestone Apr 6, 2018
stanislas-m pushed a commit that referenced this pull request May 12, 2018
* moving to use webpack4

* adding uglifier options on the right place

* moving to use miniCSS as webpack recommends

* disabling comments from production build js

* adding back babel env as preset

* removing transition

* using forEach
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants