This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of less-loader.
Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
If you've already configured your resolve.alias with a .less extension, you can now remove that wrong extension.
The root option was never documented, so it's very unlikely that this is actually a breaking change. However, since the option was removed, we need to flag this as breaking.
dependencies: Require webpack 2 as peer dependency
source-maps: Since the map is now passed as an object to the next loader, this could potentially break if another loader than the css-loader is used. The css-loader accepts both.
With Integrationsfirst-class bot support landed on GitHub and we’ve rewritten Greenkeeper to take full advantage of it. Simpler setup, fewer pull-requests, faster than ever.
Screencast Try it today. Free for private repositories during beta.
Hello lovely humans,
less-loader just published its new version 4.0.0.
This version is not covered by your current version range.
Without accepting this pull request your project will work just like it did before. There might be a bunch of new features, fixes and perf improvements that the maintainers worked on for you though.
I recommend you look into these changes and try to get onto the latest version of less-loader. Given that you have a decent test suite, a passing build is a strong indicator that you can take advantage of these changes by merging the proposed change into your project. Otherwise this branch is a great starting point for you to work on the update.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
Bug Fixes
Chores
Features
BREAKING CHANGES
resolve.aliaswith a.lessextension, you can now remove that wrong extension.The new version differs by 90 commits .
0f7d70echore(release): 4.0.0936d8dfMerge pull request #176 from webpack-contrib/docs/update-readmef44f1fbdocs: update readme3cdc410Merge pull request #175 from webpack-contrib/fix/package-json84c82feMerge pull request #174 from webpack-contrib/docs/source-map-example4077ee0chore: fix package.json issues5297675docs: add source map examplee0d0006Merge pull request #173 from webpack-contrib/fix/watch-all-importsa50f4ddMerge pull request #172 from webpack-contrib/feat/better-err-msg53c90fcfix: error where not all files were watchedcd1734dtest: fix error message tests on windows39772a5feat: improve formatting of error messages8611aceMerge pull request #171 from webpack-contrib/fix/resolve-alias0c2f385Merge pull request #170 from webpack-contrib/test/source-map2bdabf5Merge pull request #169 from webpack-contrib/feat/new-resolverThere are 90 commits in total. See the full diff.
Screencast
Try it today. Free for private repositories during beta.