dgeni-packages
dgeni-packages copied to clipboard
angular
A collection of dgeni packages for generating documentation from source code.
Hello, the current version of marked: 0.7.0 has a vulnerability described here https://nvd.nist.gov/vuln/detail/CVE-2022-21681. Can we merge https://github.com/angular/dgeni-packages/pull/331 to fix this? Thank you
Bumps [marked](https://github.com/markedjs/marked) from 0.7.0 to 4.0.10. Release notes Sourced from marked's releases. v4.0.10 4.0.10 (2022-01-13) Bug Fixes security: fix redos vulnerabilities (8f80657) v4.0.9 4.0.9 (2022-01-06) Bug Fixes retain line breaks...
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot] avatar"){kind=avatar}
Earlier `marked` versions is affected by multiple security vulnerabilities: * https://github.com/advisories/GHSA-rrrm-qjm4-v8hf * https://github.com/advisories/GHSA-5v2h-r2cx-5xgj
``` error: Error running processor "extractJSDocCommentsProcessor": Unknown node type ChainExpression. ``` would be nice if `ChainExpression ` would be supported: `var?.maybe?.existing`
Added `require('dgeni-packages/git')` to my Dgeni Package and corresponding gulp task as described in example and on run `gulp dgeni` from my project directory I get `TypeError: Cannot read property '1'...
Recently updated my Angular library project to Angular `v11.2.2` and also updated Dgeni and Dgeni Packages. Now the following error pops-up on the mentioned line of code: ``` let apiDocsPackage...
As emerged during the discussion of PR #295 some jsdoc tags (like `@module`, `@typedef` and `@callback`) should not be attatched to specific code nodes but rather they should provide information...
The [`decorateVersion`](https://github.com/angular/dgeni-packages/blob/v0.28.3/git/services/decorateVersion.js#L16) service of the `git` package contains very specific logic related to very old versions of AngularJS. This means that in case you use `dgeni-packages` to generate your project...
#### How It's Used Configure [TypeScript `compilerOptions.paths`](https://www.typescriptlang.org/docs/handbook/compiler-options.html) to resolve (and eventually display) a module path for a npm package. ``` myPackage.config((readTypeScriptModules: ReadTypeScriptModules, tsParser: TsParser) => { const typescriptPathMap: any =...
