Skip to content

[Bug?]: cannot publish to JSR when including paths that *should* be ignored #1023

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
caseybaggz opened this issue Mar 24, 2025 · 0 comments

Comments

@caseybaggz
Copy link

Problem

Unable to publish to JSR due to being denied by the "Excluded dependency" error which is incorrectly assuming it is a mistake.

Expected Behavior

JSR should allow ignoring dependencies like NPM/tsup does.

Context

My team has a flexible design system built for PandaCSS, React or SolidJS. Our PandaCSS preset is published to JSR but our component libraries (React was created before JSX was supported) are both using NPM. Our intension is to have all of our packages on JSR to provide a better DX.

With our PandaCSS preset, we can utilize the files that are generated on the users machine for our "style-system" which eliminates the need to create an unnecessary additional dependency which is what we want.

I am new to Deno so I'm hoping there is an option or configuration I'm simply overlooking?

Resources

@github-project-automation github-project-automation bot moved this to Needs Triage in JSR Mar 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Needs Triage
Development

No branches or pull requests

1 participant