Skip to content

Conversation

brittharr
Copy link
Contributor

@brittharr brittharr commented Sep 23, 2025

fixes #16819
I'm getting errors running npx changeset locally :(

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
  • Prefix your PR title with feat:, fix:, chore:, or docs:.
  • This message body should clearly illustrate what problems it solves.
  • Ideally, include a test that fails without this PR but passes with it.
  • If this PR changes code within packages/svelte/src, add a changeset (npx changeset).

Tests and linting

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

Copy link

changeset-bot bot commented Sep 23, 2025

🦋 Changeset detected

Latest commit: 4f5c2f3

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

This PR includes changesets to release 1 package
Name Type
svelte 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

Copy link
Contributor

Playground

pnpm add https://pkg.pr.new/svelte@16820

Copy link
Member

@Rich-Harris Rich-Harris left a comment

Choose a reason for hiding this comment

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

huh. I had no idea this was a thing. thank you!

I'm getting errors running npx changeset locally :(

huh, weird. Were you running it inside packages/svelte? it needs to run in the repo root. either way, i gotchu

@Rich-Harris Rich-Harris merged commit 562623d into sveltejs:main Sep 23, 2025
14 checks passed
@github-actions github-actions bot mentioned this pull request Sep 23, 2025
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.

$props.id() output format clashes with Server Side Include format
2 participants