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
Currently, users are not able to configure the modern output file name by using the "exports" field. For example, say the following package.json was being used:
I'm not sure how often such a thing is used but I ran across it whilst running some tests. I'll write up a quick PR here. So long as "exports" is a string I think we should be safe to just use that value?
The text was updated successfully, but these errors were encountered:
Currently, users are not able to configure the modern output file name by using the
"exports"
field. For example, say the followingpackage.json
was being used:Microbundle would return
index.js
,index.example.js
, andindex.modern.js
. The fact that the user has it asindex.example-two.js
would be ignored.This, at the moment, is only customizable using
"esmodules"
, though I don't see whyexports
shouldn't work too.I'm not sure how often such a thing is used but I ran across it whilst running some tests. I'll write up a quick PR here. So long as
"exports"
is a string I think we should be safe to just use that value?The text was updated successfully, but these errors were encountered: