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
Apparently the order in which you define the development and production conditions has an effect on the resulting bundle. If you have a library with multiple entry points, let's say:
./
./core
./react
… where ./ re-exports from the sub pacakges, then index.development.mjs will point to core.production.mjs.
Apparently the order in which you define the
development
andproduction
conditions has an effect on the resulting bundle. If you have a library with multiple entry points, let's say:./
./core
./react
… where
./
re-exports from the sub pacakges, thenindex.development.mjs
will point tocore.production.mjs
.Repro: amannn/bunchee-test@cc17248
Listing
production
first is unfortunately not a viable workaround, as in this casedist/index.production.mjs
will point tocore.development.mjs
.The text was updated successfully, but these errors were encountered: