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

Add package.json "type" field #623

Merged
merged 2 commits into from
Sep 22, 2022
Merged

Conversation

julienchazal
Copy link
Contributor

This change makes Glide compatible with Node > 15

Within a package, the package.json "type" field defines how Node.js should interpret .js files. If a package.json file does not have a "type" field, .js files are treated as CommonJS.

A package.json "type" value of "module" tells Node.js to interpret .js files within that package as using ES module syntax.

This change makes Glide compatible with Node > 15

Within a package, the package.json "type" field defines how Node.js should interpret .js files. If a package.json file does not have a "type" field, .js files are treated as CommonJS.

A package.json "type" value of "module" tells Node.js to interpret .js files within that package as using ES module syntax.
@julienchazal
Copy link
Contributor Author

see #620

@jedrzejchalubek
Copy link
Member

Looks like the build is failing as adding this property requires to use of ESM export/import module syntax. Probably jest.config.js just need to use export default instead of module.exports =

@jedrzejchalubek jedrzejchalubek merged commit 5b8bfe5 into glidejs:master Sep 22, 2022
@julienchazal julienchazal deleted the patch-1 branch September 22, 2022 14:54
@julienchazal
Copy link
Contributor Author

thanks @jedrzejchalubek 👍

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 this pull request may close these issues.

2 participants