Design Meeting Notes, 9/20/2023

[DanielRosenwasser]

Import Attributes

#54242

• Semantics?
• Parse and ignore these except for the resolution-mode attribute which is only respected in import type.
  • Same semantics as today with import assertions.
  • But we'll ungate them!
• Would be more ideal if resolution-mode was named the same as whatever Node.js decides... if they ever do want to include this.
• Syntax?
  • Could change to restrict bigints.
  • Would be better for us, less API churn.

JSDoc Skipping API

#55739

(continued from #55754)

• Request for finer tuning on which kinds of comments to drop/include.
• Sometimes don't care about @see and @link in TS files, but do care for JS (check this @jakebailey)
• [[Review of code]]
• Do we really need to add another parameter?
  • Move it to the options bag.
  • It starts to cascade in inconsistent ways due to capturing values via closures.
  • It looks like this 12f5903#diff-12a6724be007eb1a19d80018c7a63bbc73525ca793a9b3e5da49a4e86bbf457c

TSServer watch plugins versus protocol watching

#54012
#54662

• The feedback was that plugins are a bit round-about.
• Also, scope creep-ish issues - "watch plugins for TSServer" became "watch plugins for the compiler" which made us start discussing plugins more broadly.
• What's wrong with file events over the protocol?
  • Some inconsistencies in understanding of globs, symlinks, etc.
  • Can't recall specifics.
• Are we just not doing anything for tsc --watch?
  • Optional peer dependency on parcel's watcher?
  • Other orchestrators are able to provide their own --watch modes.