jsynowiec

5 ms·

1.
Show HN: Unique array values, performance rundown for Node.js v6 and v7(medium.com)
1 points by jsynowiec 10y ago|0 comments
2.
Show HN: Why you should always quote your globs in NPM scripts(medium.com)
1 points by jsynowiec 10y ago|0 comments
3.
by jsynowiec 10y ago
The alternative refers to an alternative type checking system - Flowtype. Not that the seconds has the async/await and modules. Both repositories are trying to deliver quite similar tools - type checking, es6 + async/awat + import
4.
by jsynowiec 10y ago
Re 1: This is not a problem with TypeScript, but with Node. It's the same with every to-js-transpiled language. You can use https://github.com/evanw/node-source-map-support to get stack traces for your TS sources.
5.
by jsynowiec 10y ago
Don't forget about PayPal! You can find some valuable informations about why Node.js is relevant in this article: http://thenewstack.io/enterprises-embracing-microservices-no...
6.
by jsynowiec 10y ago
Exactly. TSC usually complains on all stubs, mocks and spies or it takes massive amounts of time to properly annotate the types. Unit tests quickly don't follow AAA rule, are hard to read (and understand) and the required time investme
7.
by jsynowiec 10y ago
I'm using both TypeScript and Flowtype for my projects, hence the second boilerplate repository on GitHub: https://github.com/jsynowiec/node-flowtype-boilerplate Usually I tend to lean towards TypeScript due to: -
8.
Show HN: Boilerplate for Node.js and TypeScript with Jest tests(github.com)
33 points by jsynowiec 10y ago|29 comments