Skip to content

Conversation

tzdesign
Copy link

Hi there,

we are also working with changesets, but in our current project there are packages that generate package.json files within the build process that do not have a name.

These files are used for module types like:

{
  "type": "module"
}

Unfortunately there is no way to ignore them, neither with you nor with changesets. I thought I'd do a PR, let me know if there's anything else I should change here.

When you release a new version, I will also make a PR in changesets project, so that you can pass on the value via the config.

Thanks in advance

Copy link

changeset-bot bot commented Jun 23, 2025

🦋 Changeset detected

Latest commit: 425b70e

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
@manypkg/get-packages Minor

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@tzdesign
Copy link
Author

@emmatown who is in charge here?
In a few cases you have some valid package.json with no name for telling node a type.

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.

1 participant