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

Use better merge method for Webpack Preset config #2084

Merged
merged 1 commit into from
Aug 12, 2018

Conversation

knowler
Copy link
Member

@knowler knowler commented Jul 18, 2018

Using merge.smartStrategy with 'module.loaders' = 'replace' to load the preset config allows presets to override the the default webpack config. This is necessary for the coming Tailwind preset which requires resolve-url-loader and source maps to be disabled.

Using `merge.smartStrategy` with `'module.loaders' = 'replace'` to load
the preset config allows presets to override the the default webpack
config. This is necessary for the coming Tailwind preset which requires
`resolve-url-loader` and source maps to be disabled.
@knowler
Copy link
Member Author

knowler commented Jul 19, 2018

After further testing, this method doesn't work. 👀 I will look into this...

@knowler
Copy link
Member Author

knowler commented Jul 20, 2018

So this does work, but just not as much as we'd like it to. webpack-merge can't seem to remove individual loaders. We were able to silence the warnings in roots/sage-installer#22. This PR is required for that one to merge though.

@QWp6t QWp6t merged commit 157c97b into master Aug 12, 2018
@QWp6t QWp6t deleted the mod-webpack-config-preset branch August 12, 2018 02:32
ptrckvzn added a commit to ptrckvzn/sage that referenced this pull request Sep 18, 2018
* master: (64 commits)
  9.0.5
  Update comment [ci skip]
  Workaround for Bootstrap incompatibility with webpack. Fixes roots#2017
  Force `illuminate/support` to `5.6.*`
  9.0.3
  Revert "Add searchform partial and function to replace default WordPress functionality"
  Unescape get_language_attributes()
  Revert "Final filter that renders template should have PHP_INT_MAX priority."
  $comments_template fix
  Patreon
  Final filter that renders template should have PHP_INT_MAX priority.
  Add data from controller to comments template
  9.0.2
  Update dependencies
  Update to Bootstrap 4.1.3
  Bump sage-installer
  Fix
  Update composer.json
  UglifyJs: Change the ecma option from 8 to 5
  Use smartStrategy to replace loaders with preset (roots#2084)
  ...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants