feat(api): enrich generated configuration page - #198
Conversation
- add a webpack.config.js example to every option, derived from the schema (enum literals, required-object expansion, richest-shape preference for multi-shape options) - expand sub-options of multi-shape options (e.g. cache) using their richest object shape - document shared discriminators as the union of their variants (cache.type: "filesystem" | "memory") - mark deprecated options with a "Stability: 0 - Deprecated" banner
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
⚡ Lighthouse reportAudited the Vercel preview deployment: https://webpack-doc-8bb836lql-openjs.vercel.app
|
|
Hmm, I don't think the Lighthouse part is really caused by my changes anymore. It seems to be coming from Doc Kit now |
The size of the page is directly correlated to the size of the JavaScript. It's a doc-kit issue that's on my "fixing this will be great but I have zero idea how". Might be time for me to stick Codex or Claude on it, we have those tools for a reason :-) |
|
For what it's worth our JavaScript isn't render blocking, so while it affects performance in Lighthouse, it's not something that the end users will really notice, i.e. a slow machine will not make the page any slower |
|
After this, I'm going to start typing webpack defaults so we can show the default values in the documentation. |
moshams272
left a comment
There was a problem hiding this comment.
Nice work! Actually, when I worked to improve the lighthouse, I found there is more from doc-kit, so it can be as Aviv mentioned.
Summary
What kind of change does this PR introduce?
Did you add tests for your changes?
Does this PR introduce a breaking change?
If relevant, what needs to be documented once your changes are merged or what have you already documented?
Use of AI
yes!