If you had trouble reading the code examples in the 3.4 RC blog post, it should be fixed now. Thanks for pointing out the issues!https://twitter.com/typescriptlang/status/1106686406565355520 …
-
-
Show this threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
const context is beautiful... propagated generic type arguments is beautiful... It's all beautiful. I THINK THIS IS A VERY BEAUTIFUL RELEASE THAT IS WHAT I THINK
-
Why do cool type systems make me feel emotions?
End of conversation
New conversation -
-
-
@drosenwasser What was the reasoning behind default path for .tsbuildinfo? I think that putting it in out folder basically means that they very easily can end up pushed to NPM registry which is pointless. Am I missing something? -
Personally, I stopped using .npmignore files and started "whitelisting" dirs in package.json but with these settings, tsbuildinfo would become part of my package :(
- 1 more reply
New conversation -
-
-
I think the example with “foo.contents.push(5)” is missing a “as const” somewhere

-
I wonder why they decided to make it 'as const', not 'as readonly'. It's a new syntax that adds 'readonly' modifiers...

- 1 more reply
New conversation -
-
-
The 'syntax formatting' of the code in the article is showing the <span>s etc, looks like it might be double parsed. Just letting you know :)
-
Some migration friction. Should be fixed now.
- 1 more reply
New conversation -
-
-
@drosenwasser Thanks for another great release! Should incremental cache be pushed to git?! I guess that’d speed up CI builds too. Any downsides in doing that? -
I'd be very wary of pushing the incremental file into source control. It contains, or may contain, timestamps which don't translate from system to system. File under "Might work but definitely no guarantees"
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.