-
Notifications
You must be signed in to change notification settings - Fork 42
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
Add ESM Script Documentation #644
base: main
Are you sure you want to change the base?
Conversation
Co-authored-by: Will Eastcott <[email protected]>
Co-authored-by: Will Eastcott <[email protected]>
Co-authored-by: Will Eastcott <[email protected]>
Yep, at least for consistency 'Classic' might be sufficient. My only concern is that we want to push a single route moving forward, and ESM/Classic doesn't necessarily communicate that. Maybe Next/Classic? @willeastcott any thoughts here? |
I would go for Classic and Modern perhaps. |
I'm not a fan of 'Modern'. I like these two options close to equally:
|
Technically they are not ES5, as you can use classes without ESM. |
True. |
i18n/ja/docusaurus-plugin-content-docs/current/user-manual/scripting/esm-scripts.md
Outdated
Show resolved
Hide resolved
Co-authored-by: Donovan Hutchence <[email protected]>
This PR updates the documentation with the following
I confirm I have read the contributing guidelines and signed the Contributor License Agreement.