-
Notifications
You must be signed in to change notification settings - Fork 34
chore(deps): bump fast-xml-parser from 4.5.1 to 5.0.6 [POC] #3278
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
Conversation
Bundle size decrease to confirm IIFE 978.59 kB (decrease: ~6kB) TODO Angular example: f-x-p can be removed from the list of commonjs package!
…monjs) This reproduces the pb seen when running the unit and integration tests
…monjs) This reproduces the pb seen when running the unit and integration tests [skip ci]
🎊 PR Preview 8c2aa72 has been successfully built and deployed to https://process-analytics-bpmn-visualization-js-doc_preview-pr-3278.surge.sh 🕐 Build time: 0.011s 🤖 By surge-preview |
🎊 PR Preview 8c2aa72 has been successfully built and deployed to https://process-analytics-bpmn-visualization-js-demo_preview-pr-3278.surge.sh 🕐 Build time: 0.011s 🤖 By surge-preview |
This reverts commit d130a34.
|
#3295 has been merged into master, so this POC is no longer needed. |
Status: ✅
fast-xml-parser now provides ESM supports, so this improves the tree shaking. This will also remove a warning when integrating bpmn-visualization in Angular application (it complains about usage of commonjs dependencies).
First tests show that the bundle size decrease. IIFE minified is now:
To simplify dependencies management, we don't declare strnum in the package.json. This is a transitive dependency (bpmn-visualization doesn't use it directly in the code), so it is easier to let fxp manage this.
Fixing unit test execution when coverage is enabled
After bumping fxp to v5, unit tests fail on GH Action when running with coverage (at least on Ubuntu), similar to #2933 (review)
It has been reproduced locally and also on macOS.
The first try was to switch from ts-jest to @swc/jest to see if the problem came from ts-jest. The problem remained.
The root cause of the problem was that some babel dependencies (such as the core) used version 7.16, while others used version 7.26.
Aligning all dependencies to v7.26 solved the problem.
Detected issues and provided PR to f-x-p as part of this POC
Tasks