-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot scan some TypeScript compiler CJS output #37
Comments
This code was generated from using the Typescript 4.1.5 compiler outputting to cjs, by setting The source code that produces the output in
|
Looks like TS changed its output in TS 3.9.x. Contrast 3.8 output vs 3.9 output. microsoft/TypeScript#35967 and rollup/plugins#556 seem related |
Turns out this is a duplicate of #31 and not actually related to the TypeScript output change but the trailing comma added to the property definition. Will aim to backport the fix on Node.js as far as possible, but bear in mind Node.js 12 support isn't assured at this point. |
Great hunting. Thank you @guybedford! Turns out "output from tsc" and "output from tsc, then unknowingly ran though prettier" are two subtly different things. Sorry for making that confusing :) |
/cc @BPScott
https://unpkg.com/@shopify/[email protected]/dist-modern/index.js
cjs-module-lexer properly scans
__esModule
, but does not scancolorFactory
. Is this expected? If so, is the presence ofget
instead ofvalue
also enough to indicate an export?The text was updated successfully, but these errors were encountered: