Open
Description
It currently takes about fifteen seconds to build the cheatsheet, which is long enough to make it too painful to do it every time we want to run the extension in debug mode locally. As a result, we don't build the cheatsheet locally unless the user specifically runs pnpm build
. Instead, we just allow the extension to run without the cheatsheet during local development.
We should either speed up the build or use some sort of caching so that it only needs to be built once if the cheatsheet itself hasn't changed.
So we should do one or both of the following:
- Speed up the cheatsheet build by switching to
esbuild
. Note that we're currently using a couple webpack plugins to enable us to bundle into a single html file, so it might not be easy to just make this work out of the box.- One possibility would be to just run esbuild first and then just give webpack the bundled code, only relying on it todo the final bundling into an html file.
- Another possibility would be to just do the final html construction step ourselves. It should be fairly easy with a templating engine.
- Add caching so that the cheatsheet only needs to be built once if it hasn't changed. We could do this via #1303