-
-
Notifications
You must be signed in to change notification settings - Fork 272
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
TypeScript not working #2452
Comments
@irustm sorry I misunderstood your comment previously, if you want to investigate this that would be amazing. The first step would be to work out what TypeScript code path is trying to load the global types, and to see why that codepath isn't working in the jspm conversion. This sounds like a typical conversion bug though, since it's likely a dynamic require scenario, where ideally we want to convert dynamic requires into dynamic imports for the conversion. The hard part about that though is that it likely isn't an async function. This is also related to https://jspm.org/docs/integrations#one-weird-trick-to-support-jspm-in-tools. The static analysis does support wildcards like |
omg, > jspm install -g typescript
err TypeError: Cannot read property 'warn' of undefined
at Project.checkGlobalBin (/Users/irustm/.nvm/versions/node/v11.14.0/lib/node_modules/jspm/lib/project.js:138:22) |
Woah, thanks. Fixed in dbf8fde. |
I also went ahead and fixed the support for TypeScript in cdf7144. So |
Released in 2.0.0-beta.4. |
when run gives the following errors:
The text was updated successfully, but these errors were encountered: