Yep seems to be just that we need a new typescript package.
I copied the meteor typescript package into my local packages and this was all resolved just fine, including the side-effect imports
Do you have an estimate for when we will get the next beta with swc-config.js
I can try this in my full app after that is in.
I also ran this test. Whenever we make changes to babel-compiler or any core package I believe, we need to release new versions of all dependent packages, in this case including typescript and any others I find. If not, these issues start to appear. Once we have a new set of fixes ready, I’ll publish a quick beta/RC with all packages using babel-compiler updated.
Thanks for all the reports and the reproducible repo, they really speed up our checks.
I tried out rc.0 and its is much closer. I am still running into some problems with some of my resolutions.
If I am just referencing my own code it seems to work fine, but imports that are referencing node_modules seem to be broken>
In my test repro the react-native-svg can be resolved fairly easily, its just an example of how the behavior doesn’t match typescript.
The react-native-localize one is a bit harder to resolve, since as far as I can tell there is no way to make Meteor prefer “.web” files. Being able to resolve .web files is a feature that I believe meteor should add (it matches how react-native does resolution going through .ios.js → .native.js → .js ) but I have been able to generally work around it.
It seems like any import mapping I have that is trying to reference node_modules just doesn’t work.