Change Details

[[ https://vitejs.dev/blog/announcing-vite5 | Vite version 5 is now out ]], and Vitepress is in its "release candidate" stage for 1.0. These are two critical dependencies for our project. We should spend some housekeeping time ensuring that Codex is compatible with the current versions of both of these packages. These changes will necessitate some more substantive changes in Codex, because Vite is dropping support for the CJS API – we're going to want to move away from `requre` and `module.exports` in most of our build code. Hopefully `vue-docgen-cli` (another key package) is compatible with this kind of usage.

[[ https://vitejs.dev/blog/announcing-vite5 | Vite version 5 is now out ]], and Vitepress is in its "release candidate" stage for 1.0. These are two critical dependencies for our project. We should spend some housekeeping time ensuring that Codex is compatible with the current versions of both of these packages. These changes will necessitate some more substantive changes in Codex, because Vite is dropping support for the CJS API – we're going to want to move away from `require` and `module.exports` in most of our build code. Hopefully `vue-docgen-cli` (another key package) is compatible with this kind of usage.

[[ https://vitejs.dev/blog/announcing-vite5 | Vite version 5 is now out ]], and Vitepress is in its "release candidate" stage for 1.0. These are two critical dependencies for our project. We should spend some housekeeping time ensuring that Codex is compatible with the current versions of both of these packages. These changes will necessitate some more substantive changes in Codex, because Vite is dropping support for the CJS API – we're going to want to move away from `require` and `module.exports` in most of our build code. Hopefully `vue-docgen-cli` (another key package) is compatible with this kind of usage.