undefined | Better HN

0 pointskldavis43y ago0 comments

yeah, exactly. So I wonder if ultimately they want to have the browser handle transpiling things like typescript? And I definitely think there are other concerns (such as linting) that you want to happen as part of your development pipeline.

0 comments

kamikaz1k3y ago

Browser doesn't transpile, and if you're transpiling in the browser in your own JS, you're doing it wrong...generally

Point of transpiling is improving DX, so it has no business being done during users browser render.

kldavis4OP3y ago

Sorry - I miswrote that - I meant the browser directly compiling (JIT) typescript

whstl3y ago

There is an ES39 proposal to allow type annotations in Javascript, that would allow the browser to handle TS/Flow files without needing a compile step:

https://github.com/tc39/proposal-type-annotations

(That's only to allow the type annotations to be there, not to have static checking in the browser)

IMO: I would love to see this implemented. Linting and typechecking should be ran before committing code or deploying, but I want to be able to stop transpiling/bundling in all cases.

deckard13y ago

that sounds needlessly wasteful. You can trivially strip TS out of JS before sending off to the client. You're still going to need to check TS in the build/CI step (i.e. the time consuming part) before doing anything so you've gained exactly nothing.

whstl3y ago

"You can trivially strip TS out of JS before sending off to the client"

To quote you, that sounds needlessly wasteful to me. Also I prefer not needing to deal with SourceMaps or different source when debugging. So it's quite the contrary: I gain a lot. Different strokes for different folks.

1 more reply

temp_account_323y ago

I feel like this is what everyone actually wants. Typescript in the browser (at least for me personally) would be awesome, and if they made TS into a separate language with its own runtime, that would be like the holy grail.

j / k navigate · click thread line to collapse

0 comments

kamikaz1k3y ago

Browser doesn't transpile, and if you're transpiling in the browser in your own JS, you're doing it wrong...generally

Point of transpiling is improving DX, so it has no business being done during users browser render.

kldavis4OP3y ago

Sorry - I miswrote that - I meant the browser directly compiling (JIT) typescript

whstl3y ago

There is an ES39 proposal to allow type annotations in Javascript, that would allow the browser to handle TS/Flow files without needing a compile step:

https://github.com/tc39/proposal-type-annotations

(That's only to allow the type annotations to be there, not to have static checking in the browser)

IMO: I would love to see this implemented. Linting and typechecking should be ran before committing code or deploying, but I want to be able to stop transpiling/bundling in all cases.

deckard13y ago

whstl3y ago

"You can trivially strip TS out of JS before sending off to the client"

1 more reply

temp_account_323y ago

j / k navigate · click thread line to collapse