tiktok / rush-plugins Goto Github PK

License: MIT License

JavaScript 9.36% Makefile 0.29% TypeScript 89.68% Shell 0.66%

rush rushstack rush-plugins

rush-plugins's Introduction

This repo hosts a collection of third-party plugins for RushJS.

rush-init-project-plugin

When you want to create a new project in your monorepo. There are highly chances you need copy and paste from a project already inside your monorepo. Why not reuse them, like create a project template and used in your monorepo. Yes, rush-init-project-plugin is for you!

rush-upgrade-self-plugin

When you maintain a Rush.js managed monorepo, and you write some toolkit based on rush related module, such as microsoft/rush-lib, @rushstack/node-core-library. Things become trivial if you want to upgrade Rush.js to latest version. You need keep the versions of those dependencies in consistency. rush-upgrade-self-plugin comes into rescue, it aims to help you upgrade/downgrade Rush.js version in one line.

rush-sort-package-json

This plugin leverages the great work of sort-package-json to sort package.json in your monorepo, and keep it consistent.

rush-lint-staged-plugin

Are you finding alternative to husky in your monorepo? Rush takes care of Git hooks natively by sync hook scripts under common/git-hooks/ folder into .git/hooks. So, all you need is lint-staged. Use this plugin to setup lint-staged in your monorepo!

rush-print-log-if-error-plugin

Sometimes build errors are collapsed in a remote machine, use this plugin to print the entire log if error occurs.

rush-archive-project-plugin

After you have tons of project in monorepo, install time gets slower, manage dependencies becomes harder, while some projects are eventually inactive. You just want a way to archive projects properly, and maybe retrieve one day :) Now, it's time to give this plugin a try!

rush-audit-cache-plugin

Use of rush build cache is a great way to speed up your build. But, how to know if the configuration for cache is working as expected? This plugin is for you!

rush-git-lfs-plugin

Git LFS was commonly used to managed large files/binary files in your git repository. This plugin can help you to check if newly added files are correctly managed by Git LFS and prevent users from wrongly commit their local large files.

Contributors

Stargazers

Watchers

Forkers

escapeb daveparslow

rush-plugins's Issues

`rush init-project` would encounter error "Option moduleResolution" must be set to Node 16 xxx" if npm/pnpm have not install typescirpt globally

Hi there we encounter an error while running rush init-project command:

After installing typescript globally pnpm install -g typescript it is fixed, any idea about what cause this problem?

[rush-init-project-plugin] rush update generates files with windows newlines (CRLF) on MacOS

Summary

Running the rush update on MacOS causes the command-line.json file in autoinstallers directory to change the line format to Windows lines (CRLF).

Repro steps

Be on MacOS (or presumably *nix would have the same issue)
Run rush update
Look at the generated files. They all use windows newlines:

*/autoinstallers/*/rush-plugins/rush-init-project-plugin/rush-init-project-plugin/command-line.json

Expected result: These files should use Unix (LF) style newlines (i.e. \n)

Actual result: These files use Windows (CRLF) style newlines (i.e. \r\n)

Details

Question	Answer
@microsoft/rush version	5.90.2
rushVersion	5.90.2
Operating system	MacOS 14.1.1
Node.js version	18.18.2

rush-init-project-plugin fails for typescript init.config files

If you use the documented setup for init.config.ts, the plugins internal ts-node build fails with the following error:

Starting "rush init-project"

? Please select a template node-lib
Hello from template configuration! "node-lib" /Users/michaelsitter/dev/web-projects/common/_templates/node-lib
⨯ Unable to compile TypeScript:
error TS5109: Option 'moduleResolution' must be set to 'Node16' (or left unspecified) when option 'module' is set to 'Node16'.

I think I managed to track the failure down to this line in TemplateConfiguration. I experimentally added module: 'none' & it resolves this issue, but it's not clear to me what should actually be happening here. Is ts-node supposed to be discovering a tsconfig file at this step, or is this intentionally hardcoded in the plugin?

I have a branch which reproduces this issue here: https://github.com/MichaelSitter/web-projects/tree/rush-init-project-ts-config-repro