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 using TypeScript w/ Polyserve or PWA-starter-kit, the correct JS generated using TS 3.7 features get re-written in a weird way by the dev server pipelining leveraged by polymer serve:
foo?.someProp??"default value"
gets re-written as invalid JS:
foo ? .someProp ? ? "default value : : :
The errors that populate involves babylon. Because of these errors, you have to stop the dev server constantly to re-run tsc to generate the correct code.
The text was updated successfully, but these errors were encountered:
lozandier
changed the title
Polyserve tool re-writes correct JS generated by TS 3.7 to invalid synax when null coalesce & optional chaining is used
Polyserve tool re-writes correct JS generated by TS 3.7 to invalid synax when null coalesce & optional chaining is used
Nov 12, 2019
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
When using TypeScript w/ Polyserve or PWA-starter-kit, the correct JS generated using TS 3.7 features get re-written in a weird way by the dev server pipelining leveraged by
polymer serve
:gets re-written as invalid JS:
The errors that populate involves
babylon
. Because of these errors, you have to stop the dev server constantly to re-runtsc
to generate the correct code.//cc @rictic
The text was updated successfully, but these errors were encountered: