Open perbergland opened 1 year ago
OK it seems as if the fallback path simply is not used. I could work around most of the problems by adding explicit overrides for meteor packages that are NOT in .meteor/local/types
"preserveSymlinks": true,
"baseUrl": ".",
"paths": {
"meteor/blaze": ["node_modules/@types/meteor/blaze.d.ts"],
"meteor/http": ["node_modules/@types/meteor/http.d.ts"],
"meteor/react-meteor-data": [
"node_modules/@types/meteor/react-meteor-data.d.ts"
],
"meteor/tools": ["node_modules/@types/meteor/tools.d.ts"],
"meteor/*": [
".meteor/local/types/packages.d.ts",
"node_modules/@types/meteor/*"
]
},
zodern:types
had originally added entries to packages.d.ts for types in @types/meteor, which allowed types in core packages to be preferred, and it to fallback to types in @types/meteor. However, this caused some types from @types/meteor to be missing, such as MongoInternal, so I removed it in https://github.com/zodern/meteor-types/commit/7c920799cd4d8241d974e176f57e87706789f759. Now that most core packages have types, it might be worth re-adding it.
I will look into the issues you found.
This seems to be the same issue as in #5 .
Since only some meteor/XX packages have types, we need to get a mix of retrieving types from node_modules/@types and .meteor/local/types.
Unfortunately I cannot get this to work.
When prioritizing types in node_modules over the ones in .meteor/local as per usage instructions, I get a bunch of errors:
When switching the order, I get different errors (mostly for core packages like blaze and react-meteor-data that don’t have published types in meteor 2.9.1: