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
Hi guys, I was wondering whether there are any plans to make the parsers tree-shakable? For example, by introducing a new parsing API that allows a Parser instance to be passed explicitly as a replacement for the current dynamic parser resolution, or by exposing separate parse functions for each supported parser.
As a workaround, I could detect which parsers are used at the application level and replace unused parsers with an empty object export during the build process, but we should avoid such hacky solutions due to the maintenance overhead.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys, I was wondering whether there are any plans to make the parsers tree-shakable? For example, by introducing a new parsing API that allows a Parser instance to be passed explicitly as a replacement for the current dynamic parser resolution, or by exposing separate parse functions for each supported parser.
As a workaround, I could detect which parsers are used at the application level and replace unused parsers with an empty object export during the build process, but we should avoid such hacky solutions due to the maintenance overhead.
Beta Was this translation helpful? Give feedback.
All reactions