You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
> 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
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)
The text was updated successfully, but these errors were encountered: