@sveltejs/package Allow disabling the default behavior of copying package.json to the output directory when packaging a Svelte library

[bryanmylee]

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

• It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
• This message body should clearly illustrate what problems it solves.
• Ideally, include a test that fails without this PR but passes with it.

This resolves #6824.

For context, I'm building a cross-framework component library so I've set up a standard package structure for each framework in my monorepo with npm workspaces.

I'm using Vite with @sveltejs/package to develop and build my components. However, @sveltejs/package breaks my toolchain because it creates a copy of package.json in my dist folder.

npm workspaces picks up both the original package.json and dist/package.json, causing other dependent packages to break due to the duplication.

This PR adds a copyPackageJson option to allow disabling the copy feature.

Tests

• Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

All existing tests for @sveltejs/package pass and I added a test for the new config option.

Changesets

• If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

[changeset-bot]

🦋 Changeset detected

Latest commit: bdbbb6e

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

This PR includes changesets to release 1 package

Name	Type
@sveltejs/package	Patch

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

[david-plugge]

The package command also copied the readme and changelog. What about a more general solution like an array of files and folders to copy or a filter function?

[dummdidumm]

Yes that could be a more general solution. I'm tempted to put this into files but that's currently used for project files only, not sure if that breaking change is worth it (especially since it's not easy to detect) and if that even would be a good API.

[bryanmylee]

I didn't notice the README or changelog because it wasn't affecting the monorepo, but perhaps a more general metadata field would be better?

We can make its API similar to files, except we make the distinction that files only relates to project code, while metadata refers to the extra things like README, package.json, and the changelog.

[bryanmylee]

Closed this in favor of #6864.