Andrew Bradley
Andrew Bradley
Another option: fixed `delta_time`. Effectively, your `on_update` receives a constant value no matter if your computer slows down and cannot maintain the requested framerate.
Linking to #1543
My `game_coro` implements a similar clock/subclock API. It's called "context" but similar idea: an object that tracks time and exposes it on various properties. For example, coroutines can create a...
This option probably still works in ts-node even when running on node 19. You can test it to be sure. Related to #1813
I'd like this for ts-node to emulate the behavior of node's `-p` flag. `node -p 123` is equivalent to `node -pe 123`
> In pre 20 we used to be able to wrap the ESM source and proxy props now we have to parse the source with an AST parser to get...
[`@cspotcode/source-map-support`](https://npm.im/@cspotcode/source-map-support) uses [`@cspotcode/source-map-consumer`](https://www.npm.im/@cspotcode/source-map-consumer) which is a fork of `source-map` that only has the consumer. [`@cspotcode/source-map`](https://www.npmjs.com/package/@cspotcode/source-map) includes the generator, too. These are based on the latest `source-map` version. They use WASM...
Has anyone done benchmarks of the various options? I haven't, so I really don't know if they're different: if wasm is faster/slower/whatever. EDIT: I see them in the README now....
I can migrate @cspotcode/source-map-support as well. Would be nice to consolidate the ecosystem a bit more.
This is a node issue, not a grunt or grunt-contrib-watch issue. Your version of node doesn't support arrow functions. `request.js` is only parsed _once_ when you start grunt. That's why...