ts-node cannot be used with typescript@7.
although node@24 can directly run typescript file, but stripe the types, without type-checking, also it require changing the import path with .ts, and it doesn't support import .tsx files.
852 karma · joined December 3, 2014
ts-node cannot be used with typescript@7.
although node@24 can directly run typescript file, but stripe the types, without type-checking, also it require changing the import path with .ts, and it doesn't support import .tsx files.
(At the same time, I'm happy if my site can help the AIs / its users, but I prefer it not significantly slow down my own usage. There should be a balanced combination)
Is there a neural/positive term to describe this kind of website? (beside call it "old school" or "good old day"?)
// version 1
let body = document.createElement('body')
body.innerHTML = document.body.innerHTML
// version 2
let body = document.body.cloneNode(true)
Either version can trigger the bug of the pop up menu now showing up.
The menu is able to show up if doing early return to skip that code.This is wired, that code should not be mutating existing DOM.
Update: Below version of sandboxed clone doesn't break the youtube popup menu.
// version 3
let parser = new DOMParser()
let doc = parser.parseFromString(document.body.outerHTML, 'text/html')
let body = doc.bodyThen it seems to be in conflict with some addon I'm using.
In the workplace, we're using AI anyway.
I'm not sure if this direction is suitable for kids, like we still learn to do calculation even when we have calculator (which is needed for some cases, but for complex math, we opt for tools)
And sometimes even using the exact repo name in Google search, I cannot see the corresponding (non-popular) repo.
ts-liveview is a TypeScript framework I built (grab it as a starter project on GitHub[1]) for real-time, server-rendered apps. It uses JSX/TSX to render HTML server-side and, in WebSocket mode, updates the DOM by targeting specific CSS selectors (document.querySelector) over WebSockets or HTTP/2 streaming. This keeps client-side JavaScript light, delivering fast, SEO-friendly pages and reactive UIs, much like Dan’s “JSX over the wire” vision.
What’s your take on this server-driven approach? Could it shake up how we build apps compared to heavy client-side frameworks? Curious if you’ve tried ts-liveview yet—it’s been a fun project to dig into these ideas!
E.g. for easier mode. It should only generate pattern that is "beneficial" to the current board.
That is to use all rgb values exactly once to make an art work.
Examples: https://allrgb.com/
Then we can review the code before actually running it.
And the reviewed result can be saved for future running.
The proxy introduced is pinggy
ssh -p 443 -R0:localhost:8000 qr@a.pinggy.io
Can I let-declare an variable in one code block, and refer to it in another code block with static type hint?
Is it possible to automate the setup process ?
It seems a viable alternative but not necessarily eliminating the problem discussed at the beginning.