JSPM support

The JavaScript Package Manager, JSPM, is a frictionless package manager for JavaScript that is able to pull packages from various sources ("endpoints", as they are called), such as Node Package Manager (NPM) and Bower. Unifying all in one interface.

It also has the ability to load EcmaScript 6 modules through the System.js library that implements a loader.

One notable feature is its support for transpilers, traceur (with AtScript) and Babel (formerly e6to5), that brings the new ES6 syntax and features and makes it easy to get started with building modern JavaScript applications.

JSPM brings a dynamic developer experience that pulls dependencies on the the fly. When an app is ready to be deployed it can then be compiled and dependencies can be bundled.

The JSPM configuration-file is based on the NPM package.json format.

TypeScript should support this new ecosystem too.

Yes please!

+1

Aurelia makes extensive use of JSPM, and having worked with both I'd 👍 this.

👍

Yes please!

Mohamed Hegazy (@mhegazy)

Mohamed Hegazy (@mhegazy) Accepting PRs?

I actually like the JSPM work flow, and we should do that :) a couple of thoughts:

we need a transpile(input: string): string interface on the TS side, to make the interaction with the API clean and simple
we need to emit into the system.js module structure, possibly a new --module system
finally plugin typescript support to JSPM

PRs are definitely welcomed

we need a transpile(input: string): string interface on the TS side, to make the interaction with the API clean and simple

I am sure you already know : https://github.com/teppeis/typescript-simple , it now does inline sourcemaps : teppeis/typescript-simple#7 (I used it for atom/atom#5898)

We have to make sure this comes out requiring zero configuration beyond any steps needed to get typescript initially installed.

Alexander Trauzzi (@atrauzzi)

Alexander Trauzzi (@atrauzzi) I was about to start work on this but noticed from : https://github.com/jspm/registry/blob/master/registry.json#L13 that there is jspm install ts from (https://github.com/frankwallis/plugin-typescript) by Frank Wallis (@frankwallis) already.

Is there something more required?

I have not evaluted the extension yet. I don't know what level of support there is.

Can you debug the TS in the browser?

I am the author of plugin-typescript and I'm currently converting a large multi-repository project over to using it.

It does provide source-maps so you can debug TypeScript in the browser.

I am very interested in any feedback people have, so if you find any issues or have suggestions for improvements you would like to see then please raise issues on that repository. I will be making some minor improvements to it over the coming week.

Where can I track support for bundling in jspm?

Mohamed Hegazy (@mhegazy)

Testing https://github.com/Microsoft/TypeScriptSamples/tree/jspm/jspm with the latest jspm beta (0.16).

I don't seem to get compile errors in the browser, e.g. this succeeds:

function greeter(person: string) {
    return "Hello, " + person;
}

var user = [0, 1, 2];

greeter(user);

/cc Mohamed Hegazy (@mhegazy)

Oliver Joseph Ash (@OliverJAsh)

Oliver Joseph Ash (@OliverJAsh) complete typechecking in transpile scenarios is not possible: TypeScript compiler deliberately works within given file without attempting to resolve any references to external files (including standard library). In this circumstances it cannot build the full set of types that will be available in the program and will report lots of errors which are in fact false positives. If you want to have full-fledged editing experience with correct errors - you should use editor with TypeScript support i.e. VSCode, Sublime, Visual Studio, Atom etc. Support to compile isolated modules can be seen as merely a shortcut to avoid explicit compilation step but not the replacement for full program analysis which can be done i.e. in the editor or the compiling the whole program.
NOTE: We consider reporting syntax errors as an option

Vladimir Matveev (@vladima)

Vladimir Matveev (@vladima) Thanks for the explanation.

I'm looking at VSCode and the IDE plugins now. Is it possible to hook these up to SystemJS so they read the config and can parse third party dependencies, e.g. import jquery from 'jquery;`?

Oliver Joseph Ash (@OliverJAsh)

Oliver Joseph Ash (@OliverJAsh) That would be simply amazing. Would almost offer a first-class client side dev experience.

I'm fairly curious about this, because I feel like there are numerous undiscovered challenges:

If it's a pure JavaScript package, how far can the hinting really expect to go?
If it's a TypeScript package, does it read built JS, or does it look somewhere for TS code?
If it's built JavaScript that includes the .r.js files, where should it expect to find those?
What if it's a package that needs to be supplemented with an r.js from another source? Any way to match the two?

Probably more questions. But I feel like package development in JS is just insanely complex and difficult to reason about with or without TypeScript.

Vladimir Matveev (@vladima)

I don't seem to get compile errors when bundling either (now supported in jspm@0.16-beta.2). /cc Vladimir Matveev (@vladima)

Tracking systemjs/builder#206

Technically bundling as it is done in jspm now is not a whole program analysis as it processes modules one by one. I already have a workitem in my list to add support for reporting syntax errors during transpile part in es6-module-loader and in systemjs/builder.

Also we already have plenty of requests to add support for bunding in TypeScript compiler - is already in the roadmap (I think it is currently scheduled for 2.0).

Currently JSPM understands typescript but the typescript compiler does not know how to resolve typings using jspm as it does with npm. This is significant for two reasons:

Running tscresults in false errors because it can't load library typings. This may be able to be resolved via typings (https://github.com/typings/typings), but only via an additional typings install.
VSCode shows a bunch of false errors in files, presumably because it relies on tsc to generate errors.

Is there meanwhile an example ?

Marc Wensauer (@daslicht)

Marc Wensauer (@daslicht) - you can see some jspm/typescript examples here

Josh Graber (@SonofNun15)

Josh Graber (@SonofNun15) Is there an issue tracking this?

Oisin Grehan (@oising)

Oisin Grehan (@oising): yes, this one

Why is this closed ? Where can we follow the progress on this ?

It is closed because as mentioned above it is supported.

There are the Microsoft/TypeScriptSamples which maybe a better place to focus your questions/look for answers.

Navigation Menu

Repository navigation

JSPM support #2233

36 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

JSPM support #2233

Description

Activity

red010b37 commented on Mar 9, 2015

robcleghorn commented on Mar 9, 2015

RichiCoder1 commented on Mar 10, 2015

atrauzzi commented on Mar 13, 2015

ejsmith commented on Mar 17, 2015

RyanCavanaugh commented on Mar 17, 2015

mhegazy commented on Mar 17, 2015

basarat commented on Mar 17, 2015

atrauzzi commented on Mar 17, 2015

basarat commented on Mar 18, 2015

marinasundstrom commented on Mar 18, 2015

frankwallis commented on Mar 18, 2015

36 remaining items

OliverJAsh commented on Jun 12, 2015

OliverJAsh commented on Jun 14, 2015

vladima commented on Jun 14, 2015

OliverJAsh commented on Jun 15, 2015

atrauzzi commented on Jun 15, 2015

OliverJAsh commented on Jun 19, 2015

vladima commented on Jun 19, 2015

SonofNun15 commented on Feb 20, 2016

daslicht commented on Mar 2, 2016

frankwallis commented on Mar 2, 2016

oising commented on Mar 26, 2016

SonofNun15 commented on Mar 28, 2016

Bretto commented on Apr 27, 2016

kitsonk commented on Apr 27, 2016

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions