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

Update dependency @symfony/webpack-encore to v4 #12

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 10, 2023

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@symfony/webpack-encore ^1.6.1 -> ^4.0.0 age adoption passing confidence

Release Notes

symfony/webpack-encore (@​symfony/webpack-encore)

v4.6.1: Re-add support for Node 18

Compare Source

Hey packagers!

It seems I was a bit too quick to drop support for Node 18. This re-adds it.

Upgrading

Run:

npm install "@​symfony/webpack-encore@^4.6.1" --save-dev

Or:

yarn upgrade "@​symfony/webpack-encore@^4.6.1"

Changes: symfony/webpack-encore@v4.6.0...v4.6.1

Happy Packing!

v4.6.0

Compare Source

v4.5.0

Compare Source

v4.4.0

Compare Source

Features

v4.3.0

Compare Source

Features
Bugs

v4.2.0

Compare Source

Features
  • Allow webpack-cli version 5 to be used in your package.json file

v4.1.2: 4.1.2 - fixes Vue 2 version problem

Compare Source

Hey packagers!

This release fixes an incompatibility when using @vue/compiler-sfc with Vue 2.7. Thanks to @​dmaicher in #​1166 for the fix!

Upgrading

Run:

npm install "@​symfony/webpack-encore@^4.1.2" --save-dev

Or:

yarn upgrade "@​symfony/webpack-encore@^4.1.2"

Changes: v4.1.1..v4.1.1

Happy Packing!

v4.1.1: Fixing version typo in 4.1.0

Compare Source

Hey packagers!

A tiny release to fix a typo in 4.1.0 that made the package uninstallable.

Upgrading

Run:

npm install "@​symfony/webpack-encore@^4.1.1" --save-dev

Or:

yarn upgrade "@​symfony/webpack-encore@^4.1.1"

Changes: v4.1.0..v4.1.1

Happy Packing!

v4.1.0

Compare Source

October 17th, 2022

Features
Bug Fixes
  • Support for Vue 2 was accidentally dropped in 4.0.0, and was re-added - #​1157 thanks to @​Kocal.

v4.0.0

Compare Source

This major release makes Encore compatible with Yarn Plug'n'Play and pnpm.

BC Breaks
  • The following dependencies must be added in your package.json: webpack webpack-cli @​babel/core @​babel/preset-env (#​1142 and #​1150):
npm install webpack webpack-cli @​babel/core @​babel/preset-env --save-dev

v3.1.0

Compare Source

August 24th, 2022

v3.0.0

Compare Source

July 8th, 2022

This major release drops support for Node 12 (minimum is now Node 14) and
also bumps some dependencies up a new major version.

BC Breaks
  • In #​1122 support for Node 12 was dropped.

  • In #​1133, the following dependencies were bumped a major version:

    • css-minimizer-webpack-plugin 3.4 -> 4.0 (4.0 just drops Node 12 support)
    • less-loader 10 -> 11
    • postcss-loader 6 -> 7
    • sass-loader 12 -> 13
    • stylus 0.57 -> 0.58
    • stylus-loader 6 -> 7

If you're using any of these (all are optional except for css-minimizer-webpack-plugin
and are extended them with custom configuration, check the CHANGELOG of each for
any possible BC breaks).

Feature

v2.1.0

Compare Source

May 5th, 2022

Feature

v2.0.0

Compare Source

May 3rd, 2022

This is a new major version that contains several backwards-compatibility breaks.

BC Breaks

The following dependencies were upgraded a major version. It's unlikely
these will cause problems, unless you were further configuring this part
of Encore:

  • clean-webpack-plugin Version 3 to 4: dropped old Node & Webpack version support
  • css-loader Version 5 to 6: dropped old Node version support & CHANGELOG
  • css-minimizer-webpack-plugin Version 2 to 3: dropped old Node version support
  • loader-utils REMOVED
  • mini-css-extract-plugin Version 1.5 to 2.2.1: dropped old Node & Webpack version support & CHANGELOG
  • pretty-error Version 3.0 to 4.0: dropped old Node version support
  • resolve-url-loader Version 3.0 to 5.0: dropped old Node version support, requires postcss ^8.0, remove rework engine & CHANGELOG
  • style-loader Version 2 to 3: dropped old Node and Webpack version support & CHANGELOG
  • yargs-parser Version 20.2 to 21: dropped old Node version support

Additionally, Encore changed the supported versions of the following packages,
which you may have installed to enable extra features:

  • eslint Minimum version increased from 7 to 8

  • eslint-webpack-plugin Minimum version increased from 2.5 to 3

  • fork-ts-checker-webpack-plugin Minimum version increased from 5 to 6 CHANGELOG

  • less-loader Minimum version increased from 7 to 10

  • postcss-loader Minimum version increased from 4 to 6

  • preact Minimum version increased from 8 to 10 CHANGELOG

  • sass-loader Minimum version increased from 9 to 12

  • stylus Minimum version increased from 0.54 to 0.56

  • stylus-loader Minimum version increased from 3 to 6 CHANGELOG

  • vue-loader Minimum version increased from 16 to 17 CHANGELOG

  • Removed Encore.enableEslintLoader(): use Encore.enableEslintPlugin().

  • If using enableEslintPlugin() with the @babel/eslint-parser parser,
    you may now need to create an external Babel configuration file. To see
    an example, temporarily delete your .eslintrc.js file and run Encore.
    The error will show you a Babel configuration file you can use.

  • With configureDefinePlugin(), the options['process.env'] key format
    passed to the callback has changed (see #​960). If you are using configureDefinePlugin()
    to add more items to process.env, your code will need to change:

Encore.configureDefinePlugin((options) => {
-    options['process.env']['SOME_VAR'] = JSON.stringify('the value');
+    options['process.env.SOME_VAR'] = JSON.stringify('the value');
})

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Contributor Author

renovate bot commented Mar 10, 2023

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm notice 
npm notice New major version of npm available! 8.19.4 -> 9.6.1
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v9.6.1>
npm notice Run `npm install -g npm@9.6.1` to update!
npm notice 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: bookkeeping@1.0.0
npm ERR! Found: react@17.0.2
npm ERR! node_modules/react
npm ERR!   dev react@"^17.0.2" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer react@"^18.0.0" from @testing-library/react@14.0.0
npm ERR! node_modules/@testing-library/react
npm ERR!   dev @testing-library/react@"^14.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate-cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2023-03-10T04_17_46_963Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants