-
Notifications
You must be signed in to change notification settings - Fork 15
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
[V3] Used named import for fast-xml-parser
#170
Comments
Thx for your help, I will upgrade to 14.19 all the same. |
@ellis2323 This is just a ticket I created so I won't forget to revert today's change in 2023 when I drop node 14 support. The latest version of |
fast-xml-parser
fast-xml-parser
# [3.0.0-next.2](v3.0.0-next.1...v3.0.0-next.2) (2023-02-04) ### Bug Fixes * use named import for fast-xml-parser ([#273](#273)) ([314e786](314e786)), closes [#170](#170) ### Features * do not use/export enums ([#274](#274)) ([ce27203](ce27203)) ### BREAKING CHANGES * `ColumnType` is not a TypeScript enum anymore: - `ColumnType` is a union type - `ColumnTypes` a map for easier usage of `ColumnType`
🎉 This issue has been resolved in version 3.0.0-next.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
# [3.0.0](v2.2.6...v3.0.0) (2023-11-28) ### Bug Fixes * `exactOptionalPropertyTypes` TS option compatibility ([#300](#300)) ([31b129a](31b129a)) * set conditional exports in package.json ([#299](#299)) ([ef65273](ef65273)) * use named import for fast-xml-parser ([#273](#273)) ([314e786](314e786)), closes [#170](#170) ### Code Refactoring * use private class fields/methods ([2fef138](2fef138)) ### Features * do not use/export enums ([#274](#274)) ([ce27203](ce27203)) * drop node 14 support ([#272](#272)) ([d44c67d](d44c67d)) * drop node 16 support ([#283](#283)) ([19bc255](19bc255)) ### BREAKING CHANGES * browser/node must support private class fields/methods * drop node 16 support * `ColumnType` is not a TypeScript enum anymore: - `ColumnType` is a union type - `ColumnTypes` a map for easier usage of `ColumnType` * drop node 14 support
🎉 This issue has been resolved in version 3.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
See #169
The text was updated successfully, but these errors were encountered: