Issues with `isolatedDeclarations` and the associated fixes in editor

[ssalbdivad]

Issues with `isolatedDeclarations` and the associated fixes in editor

[ssalbdivad]

@DanielRosenwasser Thank you very much and I'm sorry I'm a bit swamped at the moment or I would have done this initially. Apologies @RyanCavanaugh.

I have no intuitions about what is actionable here so if it's primarily #3 feel free to close this issue any time.

[RyanCavanaugh]

Sorry for the haphazard format of this issue.

I actually do need this turned into separate concrete actionable items.

[DanielRosenwasser]

I've turned (3) into its own issue: #58449

May or may not be something we can address easily.

[DanielRosenwasser]

For (4), that's a known pain-point. I'm not sure what the right solution there is. In that case, I would begrudgingly convert that to a module (or in reality I'd use an enum, but people have mixed feelings on that).

What would be nice is if we had something like

export const TIME_RATIOS: preserveinit = Object.freeze({
  ns: 0.000_0001,
  us: 0.001,
  ms: 1,
  s: 1000,
});

to say "actually preserve the entire expression in the declaration file". That means that anyone who runs this has to have Object.freeze globally in scope - which is obviously not a problem for most people in this case, but could be for certain other libraries. JSX also raises a weird question here (because now you possibly need .d.tsx).

[DanielRosenwasser]

Nobody reacted with a 😕 or 👎 on my preserveinit idea- but I'm not even sure if I like it. I might convince myself to file an issue if someone hasn't already done it.

I think the first actionable thing is to figure out where we can defer some work on these quick fixes.