-
Notifications
You must be signed in to change notification settings - Fork 206
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
Eliminate weird redundant globals.d.ts
files
#4830
Comments
Tagging @turadg @mhofman @michaelfig and please also add any of our other TypeScript enthusiasts I might have missed |
The solution is, you guessed it, move away from ambient types. A module file (containing an |
I literally don't care what the solution is. I just want somebody to make this go away. |
I think this could and should be tackled at the same time as #4560, but there may be a quicker fix. |
In the course of maintaining the virtual objects stuff, whenever a change to the
VatData
API happens (which has been happening quite a bit as it's under active development and evolving), it is necessary to perform coordinated changes to 6 separateglobals.d.ts
files in 6 separate packages:With the exception of the
xsnap
package, all of these files are identical and only declareVatData
and its related parts, and evenxsnaps
's does little more than that.This is ludicrous, annoying, and potentially dangerous.
If we can't get rid of these silly things, can we at least have just one of them in some standard place that everybody else can point to?
The text was updated successfully, but these errors were encountered: