Skip to content

Should I use it in production? #104

Closed
@aayushkapoor206

Description

@aayushkapoor206

I couldn't find any mention about it in the readme

Activity

blakeembrey

blakeembrey commented on Apr 27, 2016

@blakeembrey
Member

No, not really. In production you'd want to only be in transpile mode (you should have already type checked). If someone wants to contribute some PRs for this functionality, we can get it in. Otherwise I'd wait for #44.

added
questionSupport requests. We tend not to answer these on Github. Nowadays I convert to Discussion instead.
on Apr 27, 2016
prashaantt

prashaantt commented on Sep 28, 2016

@prashaantt

So @blakeembrey, can we now use it in production? As in

$ ts-node -F server.ts

I currently do tsc && node build/server.js, but the very succinctness and beauty of the above is totally worth it if I'll get no significant overheads over the second option.

blakeembrey

blakeembrey commented on Sep 28, 2016

@blakeembrey
Member

Definitely your choice, go ahead 😄 There's no heavy overheads.

Diluka

Diluka commented on Oct 16, 2017

@Diluka

using ts-node -F . to run ts code missing metadata. reflect-metadata can't get field's type.

tsc && node . is OK

blakeembrey

blakeembrey commented on Oct 16, 2017

@blakeembrey
Member

That make sense to me. Fast mode isn’t using type information, it’s just plain transpiling files on the fly. That’s not equivalent to tsc. Use the regular mode that is if you want type information. It’s a good point though and I can document that.

Diluka

Diluka commented on Oct 17, 2017

@Diluka

So, should I use in production?
ts-node . or tsc && node .

blakeembrey

blakeembrey commented on Oct 17, 2017

@blakeembrey
Member

That's not something I can tell you. I can tell you that loading type information has a larger overhead, but it shouldn't impact performance (only memory once started).

IAMtheIAM

IAMtheIAM commented on Dec 26, 2017

@IAMtheIAM

Hey, FYI there still no documentation mention about the --fast or -F option. I just found it here. That's something worth adding to the readme along with a basic intro about what it does, if its still a valid option. I saw somewhere that it's enabled by default, is that true?

blakeembrey

blakeembrey commented on Dec 31, 2017

@blakeembrey
Member
leotm

leotm commented on Sep 20, 2018

@leotm

The release note mentions use --type-check for type checking behaviour, but its not mentioned again in the docs?

blakeembrey

blakeembrey commented on Sep 20, 2018

@blakeembrey
Member

That’s because it was three major releases ago and the behaviour was reverted. It confused other people to not type check by default.

44 remaining items

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionSupport requests. We tend not to answer these on Github. Nowadays I convert to Discussion instead.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @mtrenker@cspotcode@prashaantt@cybercase@blakeembrey

        Issue actions

          Should I use it in production? · Issue #104 · TypeStrong/ts-node