> 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.

Question

> 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.

Opened this issue 2 years ago · 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)

Answer 1 · 2022-07-23T21:50:18.000Z

#231 (comment)

Answer 2 · 2022-07-24T21:10:37.000Z

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