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
When I upgrade from 3.1.0 to any 4.x version, the imports I have in {{ global initialization }} are placed inside the const peggyParser definition. This breaks compilation because type definitions at the end of the generated source file — which need these imports — can't then find imported types. I see no mention of this breaking change in the v4 release notes. Any suggestions please?
As a side note, if I have v4 peggyand v4 ts-pegjs I also get complaints about Cannot find module ts-pegjs/node_modules/prettier/standalone imported from tspegjs.mjs. I assume this is an ESM issue; any workaround for folk stuck (for the time being) on CJS?
The text was updated successfully, but these errors were encountered:
When I upgrade from 3.1.0 to any 4.x version, the imports I have in
{{
global initialization}}
are placed inside theconst peggyParser
definition. This breaks compilation because type definitions at the end of the generated source file — which need these imports — can't then find imported types. I see no mention of this breaking change in the v4 release notes. Any suggestions please?As a side note, if I have v4
peggy
and v4ts-pegjs
I also get complaints aboutCannot find module ts-pegjs/node_modules/prettier/standalone imported from tspegjs.mjs
. I assume this is an ESM issue; any workaround for folk stuck (for the time being) on CJS?The text was updated successfully, but these errors were encountered: