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
A follow up for #88, we currently use state.file.metadata to keep track of compiler metadata. However, state.file is internal api of babel and could change in the future. When it changes, our implementation would not work as expected.
We've also explored using plugin config option for compiler metadata bookkeeping but Babel has issues logged to cache config so that alternative isn't future safe either.
We need to have a proper future safe way for compiler metadata bookkeeping during plugin transform.
The text was updated successfully, but these errors were encountered:
This is still a think, there is a laundry list of all the technical debt that we have accumulated over the year in the compiler. Metadata gathering during the transformation is one of those.
Description
A follow up for #88, we currently use
state.file.metadata
to keep track of compiler metadata. However,state.file
is internal api of babel and could change in the future. When it changes, our implementation would not work as expected.We've also explored using plugin config option for compiler metadata bookkeeping but Babel has issues logged to cache config so that alternative isn't future safe either.
We need to have a proper future safe way for compiler metadata bookkeeping during plugin transform.
The text was updated successfully, but these errors were encountered: