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
Like bootsnap for ruby or https://github.com/bahmutov/cache-require-paths, we can make module name => file resolution go faster by injecting the map ahead of time into the managed process. Not exactly sure the fastest way to do this, but both TypeScript and esbuild know how to do this resolution ahead of time, so we may be able to do it one pass all ahead of time.
Alternatively and less desirably we could just cache the resolved path on the first run and re-use it when in --watch, but that doesn't improve first boot time which I'd like to do.
The text was updated successfully, but these errors were encountered:
Like
bootsnap
for ruby or https://github.com/bahmutov/cache-require-paths, we can make module name => file resolution go faster by injecting the map ahead of time into the managed process. Not exactly sure the fastest way to do this, but both TypeScript and esbuild know how to do this resolution ahead of time, so we may be able to do it one pass all ahead of time.Alternatively and less desirably we could just cache the resolved path on the first run and re-use it when in
--watch
, but that doesn't improve first boot time which I'd like to do.The text was updated successfully, but these errors were encountered: