You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interesting problem, it seems that esbuild doesn't want to detect changes in the project root for some reason, but if I move the .ng-doc folder inside the application directory, everything starts working correctly.
I think this is not an issue with NgDoc but rather with the experimental builder, but I will add an option to configure the path for the compiled modules folder so that you can move it inside your application and make everything work.
After adding the option, remember that you will also need to do the following:
Change the path to the @ng-doc/generated directory in tsconfig.json
Change the path to the .ng-doc/app-name/assets folder in angular.json
# [16.6.0](v16.5.1...v16.6.0) (2023-06-14)
### Bug Fixes
* **app:** decorators in API pages are displayed without a gap ([e697bd0](e697bd0))
### Features
* **app:** the copy button in the code block is now visible only when you hover the cursor ([18fae7e](18fae7e))
* **builder:** add lines highlighter. You can use this feature to highlight any line of code inside your code blocks ([66bd91f](66bd91f))
* **builder:** add option to change the output folder for the documentation application ([4069b47](4069b47)), closes [#65](#65)
* **builder:** builder adds lines to the code blocks ([c3cefcb](c3cefcb))
Is this a regression?
Yes
Description
Reproduction:
angularBuilder: "esbuild",
cache: true,
Please provide the exception or error you saw
No response
OS
macOS
Browser
Chrome
Node version
18.14.0
Anything else?
This is on the freshly released Angular 16.1.0, but I recall seeing this problem a week or so ago as well.
The text was updated successfully, but these errors were encountered: