Artem

The reason is that express-systemjs-translate should not intercept http request that systemjs sends to get [email protected], the assumption at https://github.com/Munter/express-systemjs-translate/blob/master/lib/index.js#L315 is not good enough. As a quick fix I add...

It actually works perfectly fine if I add `&& req.url.endsWith('.json') == false` to if in https://github.com/Munter/express-systemjs-translate/blob/master/lib/index.js#L315 It correctly compiles typescript on the server. Here is sample repo https://github.com/aindlq/express-systemjs-translate-typescript. Install all...

That is not a bug, that was my fault. I included full jspm.config.js into html page :( Apparently one need to include only part with mappings.

see simple example with typescript+react - https://github.com/aindlq/express-systemjs-translate-typescript I've loaded into the browser everything that is related to path mappings like `map`, `packages` etc. And keep everything that is related to...

I would say the experience is quite frustrating so far. Maybe it is only me, but I'm really struggling to understand how path/map/packages configuration makes a difference for server/client side...

@Munter some updates from my side: 1) It seems that it is possible to improve user experience for default configuration (with bundling). One just need to rewrite system.js configuration files...

@phreed Are you still going to publish the typings? fyi I'm successfully using them in my project, so far so good. Also I've made some significant improvements to them in...

Workaround is to "add" quotes: ``` CONSTRUCT { ?value } WHERE { BIND(CONCAT("\"", "A", "," , "B", "\"") AS ?value). } ``` ``` "A,B" . ```

Apparently it is with all string functions, not only `CONCAT`. But all string functions, even `STR`. ``` CONSTRUCT { ?value } WHERE { BIND(REPLACE("AA", "A", "B") AS ?value). } ```...

Also looks like in some situations `STR` produce wrong string for URI. ``` CONSTRUCT { ?b . } WHERE { BIND(STR() AS ?b). } ``` ``` . ``` I believe...