Skip to content

fix: drop obsolete pnpm allowBuilds entries and surface real format errors - #1198

Open
jycouet wants to merge 2 commits into
mainfrom
allowing-stuff
Open

fix: drop obsolete pnpm allowBuilds entries and surface real format errors#1198
jycouet wants to merge 2 commits into
mainfrom
allowing-stuff

Conversation

@jycouet

@jycouet jycouet commented Jul 25, 2026

Copy link
Copy Markdown
Contributor

Closes #1141
Closes #1166

Description

  • Drop allowBuilds for @tailwindcss/oxide and sharp - neither ships an install script anymore (workerd and better-sqlite3 still do, so they stay).
  • Formatting now runs prettier from node_modules/.bin (falling back to the package manager for Yarn PnP), and errors report stdout too. pnpm refuses to run pnpm exec after it writes set this to true or false placeholders on skipped builds, and it prints that on stdout, which surfaced as Failed to format files / unknown error.

Checklist

  • Update snapshots (if applicable)
  • Add a changeset (if applicable)
  • Allow maintainers to edit this PR
  • I care about what I'm doing, no matter the tool I use (Notepad, Sublime, VSCode, AI...)

@pkg-svelte-dev

pkg-svelte-dev Bot commented Jul 25, 2026

Copy link
Copy Markdown

Install the latest version of sv from 7e20737:

pnpm add https://pkg.svelte.dev/sv/c/7e207374166c41c96f6ed9df688ad3abaa03f033

Open in pkg.svelte.dev: https://pkg.svelte.dev/repos/cli/pr/1198

@changeset-bot

changeset-bot Bot commented Jul 25, 2026

Copy link
Copy Markdown

🦋 Changeset detected

Latest commit: 7e20737

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

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

@svelte-docs-bot

Copy link
Copy Markdown

@sacrosanctic

Copy link
Copy Markdown
Contributor

This is currently targeting main branch.

@jycouet

jycouet commented Jul 26, 2026

Copy link
Copy Markdown
Contributor Author

This is currently targeting main branch.

You think it should target version-1?
It could go in main and we sync to v1 after
I'm not sure what the best/easiest

@sacrosanctic

Copy link
Copy Markdown
Contributor

How do I decide which one to target?

@jycouet

jycouet commented Jul 26, 2026

Copy link
Copy Markdown
Contributor Author

How do I decide which one to target?

If it's related to kit3 or migration, I would say version-1

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.

Failed to format files Remove pnpm allowBuilds

2 participants