Skip to content

IBX-12891: Made the encore configs compatible with @symfony/webpack-encore 7 - #372

Open
pawlakadrian wants to merge 1 commit into
6.0from
IBX-12891
Open

pawlakadrian wants to merge 1 commit into
6.0from
IBX-12891

Conversation

@pawlakadrian

@pawlakadrian pawlakadrian commented Oct 16, 2026 •

Copy link
Copy Markdown
🎫 Issue IBX-12891

Related PRs:

Description:

Part of upgrading @symfony/webpack-encore to 7.x on 6.0 (4.6 and 5.0 stay on their encore version and keep the webpack <5.112.0 pin from IBX-12890). Encore 7 is an ES module (require() returns { default: Encore }) and getWebpackConfig() returns a Promise, so modifying its result synchronously (config.name = ..., module.rules, config managers) is silently lost.

This makes the encore config of this package work with both encore 5 and 7:

  • ibexa.webpack.richtext.config.js: modifies the config (name, url: false, config managers) once it is ready.
  • Removed configureBabelPresetEnv() setting useBuiltIns = false / corejs = false: these are the encore defaults already (false / null, and corejs is ignored without useBuiltIns), and Babel 8 used by encore 7 no longer has these options.

With encore 5 the behaviour is unchanged: the config is still returned synchronously, so 5.0 projects and 6.0 projects still on encore 5 are not affected.

For QA:

Verified locally on commerce 5.0 and 6.0 projects, all six ibexa:encore:compile steps from CI plus encore production:

Not verified in a browser yet; browser-tests regression run on 6.0: ibexa/commerce#2074.

Documentation:

🤖 Generated with Claude Code

…ncore 7

@symfony/webpack-encore 7 is an ES module and getWebpackConfig() returns
a Promise. The configs now resolve the module either way and modify the
webpack config once it is ready, so they keep working unchanged with
encore 5 while supporting encore 7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@pawlakadrian
pawlakadrian changed the base branch from 5.0 to 6.0 October 20, 2026 13:04
@sonarqubecloud

Copy link
Copy Markdown

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.

1 participant