-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: rewrite docs generation #5309
Conversation
d120c98
to
c38f101
Compare
no statistically significant performance changes detected timing results
|
Since the man and html docs were generated, and we are no longer checking in the generated markdown docs, I did a full diff between the docs in Diff from 8.17.0.tgz
|
04e7e0d
to
caf8c44
Compare
caf8c44
to
84124f7
Compare
0129eeb
to
9634b68
Compare
How are we to review changes in usage output now? It was very handy having them in source control to see for PRs. I suppose they still exist in the test snapshots for help/man? Do the full man pages exist in snapshots? |
That's a good point. I just checked and we have snapshots for config's Also docs generation will fail if anything couldn't be replaced, so if something isn't being generated properly we will learn about it during CI (or if you run |
#5309 will turn it back on
3037d35
to
f3b0c43
Compare
a17dfcb
to
2751b41
Compare
5ed2bcc
to
1bdb836
Compare
Squashed this to add some deps commits that we can update to in the docs workspace, so this should now be rebased. |
High level overview of the changes here:
|
ab0845d
to
ca707ca
Compare
ca707ca
to
17a7342
Compare
High level overview of the changes here: - The source for the docs content has moved from `docs/content/` to `docs/lib/content/`. The generated markdown is still written to `docs/content/` but that directory is now ignored from git. - All generated content sections of the docs have been removed and replaced with single placeholder html comments such as `<!-- AUTOGENERATED CONFIG DESCRIPTIONS -->` - Placeholders are replaced with generated content only as part of the `prepack` step, so generated markdown is no longer checked in to source and all docs related `make` commands have been removed - All docs (and docs related) snapshots have been moved to a single test file that outputs command usage and formats it with functions imported from `docs/lib/index.js`. So tests will fail if docs content changes until `npm run snap` is run.
17a7342
to
61d95dd
Compare
After #5309 moved docs dependencies to proudction deps, we started failing our daily audit CI check. Currently these deps are production so they are available when we run `pack`, but they don't need to be audited since they are never present in our published tarball. This change runs `audit` on the root CLI and all workspaces within the `workspaces/` directory, which are the only production workspaces.
After #5309 moved docs dependencies to proudction deps, we started failing our daily audit CI check. Currently these deps are production so they are available when we run `pack`, but they don't need to be audited since they are never present in our published tarball. This change runs `audit` on the root CLI and all workspaces within the `workspaces/` directory, which are the only production workspaces.
This moves all the dependencies of the `docs/` workspace to dev deps. I had originally moved them out of devDeps as part of #5309, but this seems to go against the grain of other tooling. We would have to special case both `audit` and `licensee` to run on a custom subset of our dependency tree. Maybe one day when all tools can be piped the output of an `npm query` this will be possible. It would be nice if we could only audit dependencies that are bundled as part of the CLI. But for now it's easier to move these to devDeps and then reinstall only the docs workspace after pruning during the publish step.
This moves all the dependencies of the `docs/` workspace to dev deps. I had originally moved them out of devDeps as part of #5309, but this seems to go against the grain of other tooling. We would have to special case both `audit` and `licensee` to run on a custom subset of our dependency tree. Maybe one day when all tools can be piped the output of an `npm query` this will be possible. It would be nice if we could only audit dependencies that are bundled as part of the CLI. But for now it's easier to move these to devDeps and then reinstall only the docs workspace after pruning during the publish step.
This moves all the dependencies of the `docs/` workspace to dev deps. I had originally moved them out of devDeps as part of #5309, but this seems to go against the grain of other tooling. We would have to special case both `audit` and `licensee` to run on a custom subset of our dependency tree. Maybe one day when all tools can be piped the output of an `npm query` this will be possible. It would be nice if we could only audit dependencies that are bundled as part of the CLI. But for now it's easier to move these to devDeps and then reinstall only the docs workspace after pruning during the publish step.
TODO: