New export type broke lots of apps
See original GitHub issueHi there,
Your 3.3.0 update just broke all of our apps. We’re using @ant-design/colors
, which uses tinycolor, and the 3.3.0 ES module exports broke our apps with this error:
import { tinycolor } from './index';
^^^^^^
Cannot use import statement outside a module
It might be an issue with @ant-design/colors
as well, but I don’t think 3.3.0 is backward-compatible with 3.2.1. It’s always better to respect semver and not make breaking changes on minor version updates 🤞
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:8 (3 by maintainers)
Top Results From Across the Web
Power Platform Solution Export and Import Issues
We review some of the issues to look out for and thinking about when moving Power Platform environments.
Read more >Fix export issues in Premiere Pro - Adobe Support
Fix issues in Adobe Premiere Pro that cause an "Error while compiling" error message when rendering or exporting.
Read more >Documentation - TypeScript 3.8
TypeScript 3.8 adds a new syntax for type-only imports and exports. ... It's going to continue to be the default, and is a...
Read more >Common issues and resolutions for Power Apps
A list of common issues and resolutions within Power Apps. ... update broken legacy name references to the new data source name after ......
Read more >Understanding Modules and Import and Export Statements in ...
To demonstrate how to use this, update your functions. js file to be a module and export the functions. You will add export...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@steezeburger since it sounds like you’re using yarn you can use resolutions https://classic.yarnpkg.com/en/docs/selective-version-resolutions/
Adding a resolution to your package.json and then running
yarn install
should fix it until they release a new version.You might also be able to add
@ant-design/colors
to your dependencies pinned to “5.0.0” and get that specific version instead of 5.1.0see also - https://github.com/ant-design/ant-design-colors/issues/77
🎉 This issue has been resolved in version 3.3.1 🎉
The release is available on:
Your semantic-release bot 📦🚀