The VSCode codebase is evidence TypeScript is built to scale further then Javascript.
if (!!process.send
Is there something I'm missing here? Why not just: if (process.send`if (x)` evaluates truthiness of `x` which in Javascript land might behave differently. I don't know how off the top of my head, but I know it's something to be cautious of in this language and its derivatives.
Is it not good enough for me? Is it failing me in some awful way that I feel compelled to change it? Maybe it should get out of the IDE business if its not good enough? Maybe become a farmer, take a break from technology
[1] - https://github.com/Microsoft/TypeScript/blob/master/src/comp...
It's also strange to me why they inline their interfaces, rather than organizing them in a common folder / module.
Looks like a class to me: https://github.com/Microsoft/TypeScript/blob/master/src/comp...
// Keep the class inside a function so it doesn't get compiled if it's not used.
I didn't know it was possible.
1. InversifyJS - DI in Typescript / JS
https://github.com/inversify/InversifyJS
2. TypeORM - as it says, might be the best ORM for nodejs projects:
https://github.com/typeorm/typeorm
3. Searchkit - ES web frontend - react + typescript
Also, thanks to the Inversify contributors for continuing to maintain and improve express-utils!
Do you know if there are any plans for allowing the http context (req, namely) to be injected into services? Similar to the IHttpContextAccessor in dotnet core?
I have some use cases for using pieces of the http context (headers) to instantiate some transient services. I started putting together my own pieces to see what I could get away with. Looks like it works okay, but I had to create a new container per request, using the `Container.parent` to link them.
the Typescript ecosystem has really come a long way
Think about it this way: a TypeScript compiler takes a bunch of text as input, and produces a bunch of text as output. That's not really special or weird, is it?
(The only hard part is the “bootstrapping problem” which is what happens when you want to write a compiler for language X using language X, but you can’t compile it because you don’t have a compiler yet.)
It's also one of the larger enterprise grade projects that i've seen done natively in TS. It pretty much uses all the bells and whistles that the language provides. Some decent patterns, and an active developer community.
There is this issue talking about production readiness with more feedback:
https://github.com/typeorm/typeorm/issues/591
You should know about quirks like this one:
http://typeorm.io/#/relations-faq/avoid-relation-property-in...
I've been spending more and more time reading the code and tracking the open issues - getting comfortable with phasing it into a production system
Ionic Framework 2+ is TS: https://github.com/ionic-team/ionic
Our new web component compiler Stencil is also TS: https://github.com/ionic-team/stencil
https://github.com/palantir/blueprint/tree/master/packages/c...
1. How has been your experience with Blueprint JS?
2. Is it possible to take a look at your work?
3. Would you recommend using it? If yes, what types of apps?
It is pretty damn thorough tho and the css is relatively minimal if you need to custom skin the components.
Yes I would recommend it highly. Just look through the components they have mostly everything covered.
It has fairly good docs: http://doc.babylonjs.com/ as well as an active forum for developers and users: http://www.html5gamedevs.com/forum/16-babylonjs/
Other options mentioned are also good - the Typescript compiler (https://github.com/Microsoft/TypeScript) is good to get started with especially if you read this Gitbook: https://basarat.gitbooks.io/typescript/content/docs/compiler...
You could also search popular typescript github projects that are more closely related to what you work on, but the Typescript compiler and Babylonjs 3d engine are both well written projects with fairly good documentation in my opinion.
Reading the NativeScript code gave me a really good impression of TypeScript, although I'm just learning it and haven't written much yet myself.
https://www.nativescript.org/using-typescript-with-nativescr...
I have a huge blob of old JavaScript cellular automata code I want to rewrite in TypeScript, but first I want to read some good TypeScript code before starting so I don't mess it up.
It has a bunch of old "frameworky" meta-programming code and data structures that I've painted myself into a corner with (see the "type definitions" comments), which I'd like to throw away and re-implement from scratch, because TypeScript is much better suited for that kind of stuff. And then there's a bunch of brute force bit bashing and number crunching code that I hope will just run without any modification and only a little repackaging, which is another nice benefit of TypeScript.
https://github.com/SimHacker/CAM6/blob/master/javascript/CAM...
That might sound dismissive of TS but it’s not, I’m just trying to get a sense on what you’re trying to learn from TS.