You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use ts-node caching VERY heavily, and I would say CoCalc massively uses it for halfway descent performance. Without caching every single project startup (in cc-in-cc dev mode) requires compiling every single ts file and will take about one minute (every single time!). Probably a lot of other things we build are much slower. Also, all kucalc manage, hub, etc., services will start up MUCH more slowly.
ts-node completely eliminated caching support, due to a problem with how hashes are computed for dependent files, which isn't an issue for our Docker images (I hope): TypeStrong/ts-node#672
The current behavior of ts-node is just to silently ignore requesting to use caching, e.g., where we write
with current ts-node it just doesn't work at all. So that's not so good.
Probably the right solution is to set this TS_NODE_TRANSPILE_ONLY environment variable for all containers where we run typescript code in production. For development, I don't know what we should do for projects when doing cc-in-cc dev -- do we want to have a special way to run them that doesn't just strip the typescript, but by default we do strip the typescript (so startup time is a second or two instead of a minute or two?).
The text was updated successfully, but these errors were encountered:
Uh oh!
There was an error while loading. Please reload this page.
See #4237
We use ts-node caching VERY heavily, and I would say CoCalc massively uses it for halfway descent performance. Without caching every single project startup (in cc-in-cc dev mode) requires compiling every single ts file and will take about one minute (every single time!). Probably a lot of other things we build are much slower. Also, all kucalc manage, hub, etc., services will start up MUCH more slowly.
ts-node completely eliminated caching support, due to a problem with how hashes are computed for dependent files, which isn't an issue for our Docker images (I hope): TypeStrong/ts-node#672
The current behavior of ts-node is just to silently ignore requesting to use caching, e.g., where we write
with current ts-node it just doesn't work at all. So that's not so good.
Probably the right solution is to set this TS_NODE_TRANSPILE_ONLY environment variable for all containers where we run typescript code in production. For development, I don't know what we should do for projects when doing cc-in-cc dev -- do we want to have a special way to run them that doesn't just strip the typescript, but by default we do strip the typescript (so startup time is a second or two instead of a minute or two?).
The text was updated successfully, but these errors were encountered: