allowWarningsInSuccessfulBuildworking? There's zero documentation and #1375 and #1485 don't really spell out how things should work. I tried putting just
command-line.jsonbut that doesn't seem to work. rush is trying to invoke
rebuildfor each package individually instead of running rush's rebuild command.
Also just found this comment in code:
// By default, the "rebuild" action runs the "build" script. However, if the command-line.json file
// overrides "rebuild," the "rebuild" script should be run.
rush rebuildwhere rush runs its typical rebuild logic, but ignores warnings?
rushxdon't forward command line args
package.jsonat the root. i believe that's explicitly a rush anti-pattern. this is definitely a bit frustrating!
bindefined in it's
package.json. It's listed as a dependency for another package in the repo (we'll call this package B). After linking everything, I was expecting to see the binary from package A listed in the
node_modules/.bin/directory of package B, but it isn't there. Binaries for other package B dependencies are present. Is this intended behavior?
(.d).tsfiles that I'm trying to document (in the end). So far I'm failing at api-extractor, since there is no main entry file as per framework design. So I created a
index.d.tsfile in which I reexport all files that I'm about to document. Yet, they never appear in
<my-lib>.api.jsonfile. Is my case supported? If so how? Or is api-extractor the wrong tool for it?
distfolder and runs
npm i- pulling from that local verdaccio server
rush publishdoesn't seem to support this workflow... but that doesn't mean that i can't iterate over my packages and reproduce that functionality. what approaches do sane people use?
rush buildhas this option:
-p COUNT, --parallelism COUNT Specify the number of concurrent build processes The value "max" can be specified to indicate the number of CPU cores. If this parameter omitted, the default value depends on the operating system and number of CPU cores.
rush build -t . --verbose(when it builds the dependency first) but builds fine when running
rush build -f . --verbose. The eslint error is on a file from the dependency.
pnpm run build
pnpm prune --prodin relevant packages works... but for some reason also removes all monorepo packages.
pnpm prune --prod)
goal: create docker images from certain modules, which reference other modules in the monorepo; without including all devDependencies (current strategy is tar dereferencing the folder, which works fine except for either devDependencies being included, or our own packages also being removed (when doing a
pnpm prune --prod)
@jlsjonas This is exactly what I'm working on in microsoft/rushstack#1078 I should have a usable prototype very soon.
Is it possible to use the api-extractor-model package in the browser? Basically, I want to build the api.json file at build time, send it to the browser, and build my documentation page in react based on that json file, and I'd like to use the api-extractor-model to make it easier to parse the file. But based on the API, it looks like you can only load an api.json file via a file system path, not via a URL or object.
@pat-son This is being investigated under microsoft/rushstack#1010 . @csr632 made some progress with it.
However I will also point out that when the Fabric/Fluent website approached this same problem, they found that it was better to make a build tool that preprocesses the .api.json files into a smaller data file that is more optimized for the requirements of the React web app. Their solution is here and the website that consumes these "page.json" files is here
microsoft/rushstackmonorepo to develop my own monorepo?
rush deployfrom this PR: microsoft/rushstack#1898