Drop Node.js 16 support and move to ESM #164
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
marcomontalbano
added
the
PR: Breaking Changes ☄️
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Discussion #167
What's inside?
Breaking changes
This library is now pure ESM.
This change may seem significant, but for most users, it's likely to have minimal impact. If your project already uses
type="module"in yourpackage.json, you're good to go.However, if your project hasn't yet made this transition, you'll need to rename your
.figmaexportrc.jsconfiguration file:adjust the command you run:
and start using
import foo from 'foo'instead ofconst foo = require('foo')to import the packages inside the.figmaexportrc.mjs. You can take a look at .figmaexportrc.example.js as an example.