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
Now that we are doing comprehensive input map analysis and decomposition, we can also possibly detect the conditional environment from the input map based on what resolutions are present.
This could also env to be defaulted correctly when not otherwise provided.
Although not full-proof, since having no env mappings would effectively lose this information, it may well provide a good enough approach to this long-standing problem.
The text was updated successfully, but these errors were encountered:
Just some notes for my future brain, we chatted about this and came to the conclusion that having an explicit "env" field in the output maps has a lot of benefits, like making users aware that import maps are environment specific by nature. On the other hand it will cause some warnings, so we should probably revisit this once jspm gets traction.
Now that we are doing comprehensive input map analysis and decomposition, we can also possibly detect the conditional environment from the input map based on what resolutions are present.
This could also
env
to be defaulted correctly when not otherwise provided.Although not full-proof, since having no env mappings would effectively lose this information, it may well provide a good enough approach to this long-standing problem.
The text was updated successfully, but these errors were encountered: