by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    William Bernting
    @wbern
    Well yeoman does offer what you need, but you shouldn't have to learn yeoman just to generate things, gulp is a better general purpose tool to learn with your efforts.
    Signed, the guy who started trying to learn yeoman, then moved on to slush, then moved ok to gulp. And I had never used gulp before.
    moved on to just gulp*
    Ray Gesualdo
    @raygesualdo
    Can someone please help me get allowWarningsInSuccessfulBuild working? There's zero documentation and #1375 and #1485 don't really spell out how things should work. I tried putting just name and allowWarningsInSuccessfulBuild in command-line.json but that doesn't seem to work. rush is trying to invoke rebuild for 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.

    Does that mean that there's no way to enable allowWarningsInSuccessfulBuild with rush rebuild where rush runs its typical rebuild logic, but ignores warnings?
    Ray Gesualdo
    @raygesualdo
    Don't mean to come across upset. Got a little frustrated at the end of the day :grinning:
    Devin Fee
    @dfee
    want to share this (open) issue: microsoft/rushstack#1232
    basically, it covers the situation i was running into yesterday where rush and rushx don't forward command line args
    @raygesualdo and I discussed workarounds yesterday, and one workaround was having package.json at the root. i believe that's explicitly a rush anti-pattern. this is definitely a bit frustrating!
    Ray Gesualdo
    @raygesualdo
    I have a package (we'll call it package A) with a bin defined 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?
    Devin Fee
    @dfee
    @raygesualdo did you try rush unlink && rush link?
    Ray Gesualdo
    @raygesualdo
    I did rush link --force. I'll try your suggestion though.
    THAT WORKED!!!
    Thanks @dfee!
    Thomas Gossmann
    @gossi
    Hey, I'm trying to use api-extractor within an ember addon. That is there is a collection of (.d).ts files 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.ts file in which I reexport all files that I'm about to document. Yet, they never appear in <my-lib>.api.json file. Is my case supported? If so how? Or is api-extractor the wrong tool for it?
    Pete Gonzalez
    @octogonz
    @gossi Could you open a GitHub issue and share a branch that repros your problem? I can take a look at it. Most likely the declarations are not being exported properly.
    Devin Fee
    @dfee
    @octogonz two questions (re: microsoft/rushstack#1232)
    1. are the "rush model" and the "npm compatible model" mutually exclusive,
    2. i'm unclear if one or the other (or both) would support the ability to run global commands (and forward arguments) -- i think that was the part i wasn't clear on.
    16 replies
    Matthew Pirocchi
    @mpiroc
    If anyone else is struggling with poor rush update perf on WSL, you can fix it by upgrading to WSL2 (currently in preview). The culprit is pnpm, which performs poorly on WSL. Upgrading to WSL2 made my rush update go from 2.5-3 minutes to 44 seconds.
    5 replies
    Thomas Gossmann
    @gossi
    @octogonz I did so: microsoft/rushstack#1864
    William Bernting
    @wbern
    @mpiroc please prioritize removing the rush model, we're at 100 modules in one of our repos and we believe you could solve several scaling problems once you leverage pnpm better. Pnpm also has a growing list of options that rush is blocking.
    I know it's hard to keep all users happy but I believe this and a way to maintain watch instances are two important things for rush.
    See this gif, it's not perfect yet but I'm trying to make a prompt that will make watch instances easier to maintain. Already asked @octogonz if it's of any interest for having inside rushjs. https://drive.google.com/file/d/1QL_Lp--lEhMwX9d5ovoih-qbgbgAwfdy/view?usp=drivesdk
    Devin Fee
    @dfee
    i came across a solution with lerna for publishing, where the author:
    1. stands up a local verdaccio server
    2. builds and publishes his packages to that server
    3. copies package.json into the dist folder and runs npm i - pulling from that local verdaccio server
    4. packaging that as an artifact.
      it seemed exhausting, yet functional. was wondering if there are bundle patterns like this that are unique to this Rush. unfortunately, rush publish doesn'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?
    Pete Gonzalez
    @octogonz
    rush publish --pack makes tarballs instead of publishing to a real NPM server -- would that be useful?
    15 replies
    Devin Fee
    @dfee
    Let me throw something together
    Devin Fee
    @dfee
    @octogonz i owe you a beer.
    Pete Gonzalez
    @octogonz
    😁
    David Lannoye
    @dlannoye
    Is there a reason the rush event hooks don't work closer to how git hooks work? I was looking at using the preRushInstall event hook to validate some conditions before the install, but any messages printed to the console are hidden and if I have a non-zero exit code rush still continues with the install.
    Pete Gonzalez
    @octogonz
    🤔 No, the hooks feature is not used very extensively in our repos. I don't know of any intentional reason why it should behave that way.
    Please open a GitHub issue, and a PR would be welcome. It's probably pretty easy to fix.
    Pete Gonzalez
    @octogonz
    @dlannoye
    Dean Verleger
    @deanbot
    Is there a config to set a maximum number of parallel processes?
    Trying out wsl on this machine and it gives me an extra process but the build is slower overall.
    Pete Gonzalez
    @octogonz
    @deanbot rush build has 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.
    If you want to configure it permanently (rather than specifying it as a command-line option), we could easily map it to an environment variable.
    Dean Verleger
    @deanbot
    Ty. Sure, that'd be even better. I'll open an issue.
    Pete Gonzalez
    @octogonz
    Dean Verleger
    @deanbot
    That was fast!
    Devin Fee
    @dfee
    This message was deleted
    Pete Gonzalez
    @octogonz
    The ts-command-line engine makes it really easy to map CLI parameters to environment variables. 😉
    ☃ Elliot Shepherd
    @elliots
    Hello! I'm having an issue where one of my modules fails to build with an eslint error when running using 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.
    It also builds fine running pnpm run build
    I wouldn't think there would be any difference in how it builds depending on if its building the dependency first or not, but it seems something is going on.
    Jonas De Kegel
    @jlsjonas
    Hi, is there a clean way to purge out devDependencies? (using pnpm internally)
    pnpm prune --prod in relevant packages works... but for some reason also removes all monorepo packages.
    Use case: optimizing our CD flow when dockerizing services where the related dependencies have no purpose being published.
    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)
    Patrick Son
    @pat-son
    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.
    Pete Gonzalez
    @octogonz

    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.

    Pete Gonzalez
    @octogonz

    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

    Patrick Son
    @pat-son
    Thanks, I'll take a look.
    Sergey Belov
    @arikon
    Hello. How can I use Rush from the custom PR or branch of microsoft/rushstack monorepo to develop my own monorepo?
    I want to test rush deploy from this PR: microsoft/rushstack#1898
    Couldn't find the docs about that.
    81 replies