Max Friedmann

Actually, that was only one of many problems, so we moved our source code bases around and don't need the paths anymore. Extending tsconfigs and using paths + rootDirs also...

I think this issue is partly done already, at least I can import parse, transform and stringify via ES6 imports in csv/lib/sync. Any reason why `//import * as generate from...

in the csv/lib/sync.d.ts, am in the wrong repo here I guess? 

Any news on this? We updated to Nx 13 recently, it did not get better automagically :D

My company desperately needs this package, so we tried forking it and getting it to run, without success (too many other dependencies to update with too much code to adapt...

Since nx cloud now offers 500 free hours we went back to using their service, so we won't continue with this package for now...

If you want to destroy it, see https://github.com/VincentGarreau/particles.js/issues/63#issuecomment-242977446

I am running into the exact same issue. I started off with the every_node deployment_strategy already, but now am curious how your setup targets the right nginx_proxy instance from outside....

We also have that problem and never found a better solution than writing a cli for that use case: https://www.npmjs.com/package/@smallstack/ng-wc-serve If you want to try it out, then please keep...

Stumbled over this issue since I used typings.install programmatically in version 0.6.x and it doesn't work anymore ;-) With v2.0.0, this works for me: ``` var typings = require("typings-core"); typings.install({...