Skip to content

The documentation should be supplemented with how old projects work properly under 7.0.0 #1585

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

Closed
1 of 4 tasks
hellohejinyu opened this issue Apr 8, 2024 · 2 comments · Fixed by #1586
Closed
1 of 4 tasks

Comments

@hellohejinyu
Copy link

Documentation Is:

  • Missing
  • Needed
  • Confusing
  • Not Sure?

Please Explain in Detail...

image

There are too many places in the project where the syntax import styles from 'xxx' is used. So for me, it would be a better solution if the project could use 7.0.0 without changing the syntax.

Your Proposal for Changes

Adding additional clarification in the Migration guide to add the following configuration to restore 6.x behavior.

options: {
  modules: {
    ...
    namedExport: false,
    exportLocalsConvention: 'as-is'
  }
}
@alexander-akait
Copy link
Member

Yeah, thank you for the issue, I will fix it

@bladeSk
Copy link

bladeSk commented Oct 4, 2024

What was the reasoning behind this breaking change? Old code can be thankfully fixed by using the options above, but all the existing guides and tutorials were instantly made obsolete and misleading. Especially considering the change in syntax is so subtle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants