Skip to content

fix(app-tools): avoid resolving ts paths from non-file parents#8545

Open
GiveMe-A-Name wants to merge 1 commit into
mainfrom
fix/issue-8516-postcss-tailwind
Open

fix(app-tools): avoid resolving ts paths from non-file parents#8545
GiveMe-A-Name wants to merge 1 commit into
mainfrom
fix/issue-8516-postcss-tailwind

Conversation

@GiveMe-A-Name
Copy link
Copy Markdown
Member

Summary

  • avoid running the ts paths loader against non-file: parent URLs, which can be introduced by PostCSS/rsbuild virtual modules when loading postcss.config.mjs
  • keep runtime alias resolution scoped to app files so the loader only participates where tsconfig path aliases are expected to apply
  • add regression coverage for the Tailwind v4 + postcss.config.mjs + tsconfig.json crash and preserve the alias runtime boundary checks

Validation

Closes #8516

Avoid applying tsconfig path resolution to non-file parents and parents outside the app dir.

Add integration fixtures and regression coverage for the Tailwind repro and runtime alias boundary.
@netlify
Copy link
Copy Markdown

netlify Bot commented Apr 14, 2026

Deploy Preview for modernjs-byted ready!

Name Link
🔨 Latest commit 08b7ae2
🔍 Latest deploy log https://app.netlify.com/projects/modernjs-byted/deploys/69ddb50e02a2570008f9d6f3
😎 Deploy Preview https://deploy-preview-8545--modernjs-byted.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.
Lighthouse
Lighthouse
1 paths audited
Performance: 98 (no change from production)
Accessibility: 100 (no change from production)
Best Practices: 100 (no change from production)
SEO: 100 (no change from production)
PWA: -
View the detailed breakdown and full score reports

To edit notification comments on pull requests, go to your Netlify project configuration.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Apr 14, 2026

⚠️ No Changeset found

Latest commit: 08b7ae2

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

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

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.

[Bug]: Error: Loading PostCSS Plugin failed: The URL must be of scheme file

1 participant