initial version of TypeScript support in jspm #735
Conversation
|
👍 |
| // having shim implies that 'typescript' module will have 'global' format | ||
| options.override = { | ||
| shim: { 'bin/typescript': { 'exports': 'ts' } } | ||
| }; |
There was a problem hiding this comment.
This needs to be committed to the jspm registry rather as a shared override - https://github.com/jspm/registry/.
There was a problem hiding this comment.
sure, I'll send a separate PR to the jspm registry repo
|
PR for adding TypeScript to jspm registry: jspm/registry#377 |
|
👍 |
|
@vladima finally merged! Thanks again for your efforts and patience. Release will follow as soon as I can this week, just IE testing and documentation to go. Happy to update the TypeScript reference when the time comes, please do update here when that happens. |
|
Awesome! I've been waiting for this. 👍 |
|
@guybedford thanks! looking forward for the official release |
|
When the official release of TS support in JSPM happens, would it it be possible to get some of the documentation updated to discuss the workflow. Even if it's just to outline similar things with a TS-specific bent. @guybedford, perhaps you can shed some light on this - but right now when working with other TypeScript packages, one would be leveraging that package's built-output. Not the raw TS code that might be included. Are there any plans or is there perhaps already a convention to use the actual |
|
@atrauzzi @frankwallis is the best person to chat to about this - I have very limited knowledge on the TypeScript workflows. |
|
What's the performance of the TypeScript integration in regards to using it in a medium to large project? For example I am concerned that compiling 100 js files in the browser may be too heavy on every page open in development. I am going for max 3 seconds from open to load of my application in development. |
No description provided.