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

Adds exports to package.json #46

Merged
merged 1 commit into from
Jan 21, 2023
Merged

Adds exports to package.json #46

merged 1 commit into from
Jan 21, 2023

Conversation

ekwoka
Copy link
Contributor

@ekwoka ekwoka commented Jan 19, 2023

solves #45

The new standard for resolving different exports is with the export key. https://nodejs.org/api/packages.html#package-entry-points

Some environments will require these to work properly.

@Shard
Copy link
Contributor

Shard commented Jan 20, 2023

Hi @ekwoka,

Thanks for pointing this out. I didn't have a good understanding of the new fields thinking the existing fields should be adequate but I also had been trying to figure out what was the cause of nested imports swapping between cjs/mjs.

I'm going to try and fix the CI for external PR's, do a little testing and we will be looking to merge this very quickly!

Cheers.

@Shard
Copy link
Contributor

Shard commented Jan 21, 2023

@ekwoka, If you want to try re-pulling develop I think the e2e tests should run correctly now. Cheers.

@Shard Shard merged commit fa417fd into userback:develop Jan 21, 2023
@Shard Shard mentioned this pull request Jan 21, 2023
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