Translation jobs broken: EntryModuleNotFoundError: Entry module not found: Error: Can't resolve 'babel'
Bug #1681402 reported by
Julie Pichon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Unassigned |
Bug Description
The translation jobs are currently broken (both updating the message catalogue, and downloading the translations). The error seem to start on merging https:/
EntryModuleNotF
BREAKING CHANGE: It's no longer allowed to omit the '-loader' suffix when using loaders.
[...]
For reference (in case an extra step is now required) the infra script used to set up react uses npm install and npm build directly:
Changed in tripleo: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
Thanks to Honza's pointers: this will most likely be resolved by https:/ /review. openstack. org/#/c/ 443137/ . It's currently failing CI, waiting for the new dependencies to be available as RDO packages on TripleO CI before it can pass.