-
Notifications
You must be signed in to change notification settings - Fork 119
chore(collaboration): added script to resolve typedoc issue #3997
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
☁️ Nx Cloud ReportCI is running/has finished running commands for commit 7ce602c. As they complete they will appear below. Click to see the status, the terminal output, and the build insights. 📂 See all runs for this CI Pipeline Execution ✅ Successfully ran 1 targetSent with 💌 from NxCloud. |
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit 7ce602c:
|
Size Change: 0 B Total Size: 1.08 MB ℹ️ View Unchanged
|
Passing run #8322 ↗︎Details:
Review all test suite changes for PR #3997 ↗︎ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔥🔥🔥 super useful improvements thank youuuu
Passing run #8321 ↗︎Details:
Review all test suite changes for PR #3997 ↗︎ |
Added a new script into package.json to run a series of commands to resolve the typedoc issue when forking the repo.
After investigation I found that if you run the typedoc command before running the build command it will output incorrect typedocs and cause large unintended and incorrect changes to various typedoc files. What is more interesting is that these incorrect changes are different per machine.
The resolution is to clean the local NX cache and run the full build and typedocs scrips. Tested locally by forking the repo multiple times.
If we see this issue in collab PRs we can now ask them to just run this to resolve the issue instead of granting write access to our repo