Skip to content

fix(pkg): use esm build as main field - #848

Merged
pi0 merged 1 commit into
nuxt:mainfrom
oraphadev:main
Jun 6, 2023
Merged

fix(pkg): use esm build as main field#848
pi0 merged 1 commit into
nuxt:mainfrom
oraphadev:main

Conversation

@oraphadev

Copy link
Copy Markdown
Contributor

This PR should resolve #379
I'm open for any kind of feedback or improvement.

@netlify

netlify Bot commented Jun 5, 2023

Copy link
Copy Markdown

👷 Deploy request for nuxt-image-v1 pending review.

Visit the deploys page to approve it

Name Link
🔨 Latest commit d7b394c

@danielroe
danielroe requested a review from pi0 June 6, 2023 08:29
@pi0 pi0 changed the title fix: ECMAScript as main fix(pkg): use esm build as main field Jun 6, 2023

@pi0 pi0 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM as quick fix thanks.

We shall add exports field and once added, revert back main to cjs because all modern node runtimes will pick exports (also in CJS environment)

@pi0
pi0 merged commit 6e9298b into nuxt:main Jun 6, 2023
@pi0 pi0 mentioned this pull request Jun 6, 2023
@github-actions github-actions Bot mentioned this pull request Jul 30, 2026
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.

Skipping sharp dependency?

2 participants