Skip to content
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

fix: Highcharts v12 side effect import sorting #219

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

frantic1048
Copy link
Contributor

Highcharts v12 introduces a new simpler way to import it's additional modules, which uses side effect imports to achieve.

By default, eslint-plugin-simple-import-sort groups side effect imports at the top of the file, which makes highcharts/modules/... being imported before highcharts, resulting in a runtime error.

To fix this, we add a custom groups config for simple-import-sort/imports to group Highcharts side effect imports after package imports.

Highcharts v12 info: https://www.highcharts.com/blog/changelog/#:~:text=When%20importing%20Highcharts%20as%20a%20node%20module%2C%20additional%20modules%20no%20longer%20require%20initialization

…er package imports

Highcharts v12 introduces a new simpler way to import it's additional modules,
which uses side effect imports to achieve.

By default, eslint-plugin-simple-import-sort groups side effect imports at the top
of the file, which makes `highcharts/modules/...` being imported before `highcharts`, resulting in a runtime error.

To fix this, we add a custom `groups` config for `simple-import-sort/imports` to group Highcharts side effect imports after package imports.

Highcharts v12 info: https://www.highcharts.com/blog/changelog/#:~:text=When%20importing%20Highcharts%20as%20a%20node%20module%2C%20additional%20modules%20no%20longer%20require%20initialization
@frantic1048 frantic1048 requested a review from liby December 17, 2024 09:02
@frantic1048 frantic1048 self-assigned this Dec 17, 2024
@frantic1048
Copy link
Contributor Author

As @lixiaoyan is concerned about the maintainability of this fix, we are considering alternative workarounds for this issue.

I am converting this PR to a draft. Once we reach a conclusion, this PR may be closed or ready for review again.

@frantic1048 frantic1048 marked this pull request as draft December 17, 2024 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants