rushstack
rushstack copied to clipboard
Monorepo for tools developed by the Rush Stack community
## Summary Running api-extractor in parallel seems to cause it to use the wrong config! Comparing the output of running two commands in parallel and in series, when run in...
## Summary If you're using the rush build cache and an invalid entry gets written, it completely derails all future builds until the offending entry is manually removed. ## Repro...
## Summary Api extractor emits incorrect canonical reference navigation paths for api items that don't have inline exports. Items that have inline exports and items that export items via `export...
## Summary For publish runs using the apply & branch options which release workspace packages, the version bump edits to package.json files are not reflected in the shrinkwrap state. This...
Currently, a basic `api-extractor.json` looks something like: ``` { "$schema": "https://dev.office.com/json-schemas/api-extractor/api-extractor.schema.json", "compiler" : { "configType": "tsconfig", "rootFolder": "." }, "project": { "entryPointSourceFile": "lib/index.d.ts" } } ``` which works great for...
The `bundledPackages` option is great for managing cross-package re-exports in a way that makes reasoning about the local API surface in a wholistic way. Unfortunately, the tooling currently fails in...
## Please prefix the issue title with the project name i.e. [rush], [api-extractor] etc. ## **Is this a feature or a bug?** - [ ] Feature - [X] Bug **Please...
## Summary When invoking `ChangeManager.createEmptyChangeFiles()` twice or more with a time frame of 1 Minute (e.g. `12:01:01 - 12:01:59`) existing files get overriden ## Repro steps The single invocations will...
## Summary When using `rush deploy` with `linkCreation: default`, everything appears correct in the `common/deploy` folder. Once I copy the contents of this folder into my docker container and execute...
## Summary [rush] Using `rush update` twice raise > ERROR: Internal Error: Cannot find installed dependency "@nestjs/common" in >"c:\xxx\node_modules" >You have encountered a software defect. Please consider reporting the issue...