-
Notifications
You must be signed in to change notification settings - Fork 12.4k
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
Design Meeting Notes, 8/3/2022 #50226
Labels
Design Notes
Notes from our design meetings
Comments
🤣 |
That must have been a typo but I like it. It stays. |
I think that was meant to be the description of why we went back and forth on what |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Granular Resolutions
#50152
node
.exports
map.node16
, people thought "oh cool, now I can use theexports
map"..js
,.mjs
, or.cts
)..ts
,.mts
, or.cts
.node
with some of the overlays that bundlers and the like support.node
mode accurately models a subset of them, and Node.js versions older than 12.conventional
/hybrid
(?) - bundler modesnode16
- you use Node.jsminimal
- something like what bundlers use, maybe custom/internal build.ts
" for my extension" is another big confusion point.conventional
have features layered on top to build up thenode16
mode?node16
, latter should useconventional
.satisfies
Operator#47920
satisfies
plays with types as comments/type annotations proposal..ts
can always be a superset of JS with types anyway.as ~ T
as PLEasE
as satisfies
as satisfied by
<satisfies Foo>expr
?as
assertions? (e.g.as (satisfies Foo)
)satisfies
for non-type purposes. There is a point where waiting speculatively in case that happens means you're just not shipping anything at all.The text was updated successfully, but these errors were encountered: