Using yarn vs npm with typescript docs

[CKGrafico]

When we want to use other TypeScript version and we do:
npm install typescript@3.5.3 -D
But when we use new features like const casting microsoft/TypeScript#29510 it does not compile.
Instead of that if we use:
yarn add typescript@3.5.3
Everything works

[facebook-github-bot]

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

[facebook-github-bot]

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

[ianschmitz]

Sorry @CKGrafico, it's not clear to me what this PR is addressing. yarn vs npm shouldn't affect whether you can use a specific feature of TypeScript. We also don't include typescript as a dependency of our packages. It is solely controlled by your application's package.json.

[CKGrafico]

If I create a project using --typescript seems that is using an old version of typescript (maybe some dependency?)
You can test using this code.

function example() {
    return [1, 'test'] as const;
}

'as const' is available since 3.5.1 if I'm not wrong.
If you install typescript using npm is not using the versions intalled, I 've reproduced this twice but maybe is only happening in our environments

[neilbryson]

We're using TypeScript with CRA + npm and it uses whatever version included in our devDependencies.

[stale]

This pull request has been automatically marked as stale because it has not had any recent activity. It will be closed in 5 days if no further activity occurs.