Skip to content
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

optimzeDeps.exclude glob support for package names #18284

Open
4 tasks done
ZelCloud opened this issue Oct 4, 2024 · 0 comments
Open
4 tasks done

optimzeDeps.exclude glob support for package names #18284

ZelCloud opened this issue Oct 4, 2024 · 0 comments

Comments

@ZelCloud
Copy link

ZelCloud commented Oct 4, 2024

Description

Instead of writing every package individually like so:

optimizeDeps: {
	exclude: [
		"@org/pkg-a",
		"@org/pkg-b"
	],
},

Could we get glob support like so:

optimizeDeps: {
	exclude: [
		"@org/*"
	],
},

also have optimzeDeps take precendece over the exclude if something is included.

This is a hassle to deal with, since every time a package that needs to be transpiled is inlcuded the config needs to be updated.

Suggested solution

optimzeDeps.exclude has glob support for package names.

Alternative

Writing everything down manually every time some thing new is installed (that needs transpilation).

Additional context

This helps make vite play much nicer with stylexjs components. Since they require transpilation in order to get the final atomic css output, and without this setup local development isnt possible.

Validations

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant