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

> Is it possible to expand node resolutions of bare module specifiers to include export conditions? While some packages are finally moving into using the technology they aren't always placing their best build in the default specifier and there is need to either point to --conditions="production" or --conditions="development" to correct this. If this is already possible, I'm likely just doing it wrong and it would be great to get some documentation added to clarify this support. #242

Open
Eldeloro1 opened this issue Jul 23, 2022 · 2 comments

Comments

@Eldeloro1
Copy link

Is it possible to expand node resolutions of bare module specifiers to include export conditions? While some packages are finally moving into using the technology they aren't always placing their best build in the default specifier and there is need to either point to --conditions="production" or --conditions="development" to correct this. If this is already possible, I'm likely just doing it wrong and it would be great to get some documentation added to clarify this support.

Originally posted by @Eldeloro1 in #231 (comment)

@Eldeloro1
Copy link
Author

#231 (comment)

@rictic
Copy link
Member

rictic commented Jul 24, 2022

This, and your other comments look a good bit like spam, copy-pasting content from other users

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

No branches or pull requests

2 participants