JS Monorepo Workspace Tools
Перейти к файлу
renovate[bot] 71a265dd84
Update devDependency gh-pages to v6 (#322)
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
2023-10-18 04:57:45 +00:00
.github/workflows Add API Extractor for better visibility of API changes (#262) 2023-03-22 13:00:28 -07:00
.vscode Add API Extractor for better visibility of API changes (#262) 2023-03-22 13:00:28 -07:00
change Update dependency commander to v11 (#320) 2023-10-18 04:55:17 +00:00
packages Update dependency commander to v11 (#320) 2023-10-18 04:55:17 +00:00
scripts Update to Node 16, update typescript, transpile to ES2022 (#317) 2023-10-17 21:33:18 -07:00
.gitattributes Add API Extractor for better visibility of API changes (#262) 2023-03-22 13:00:28 -07:00
.gitignore delete mystery package-lock.json 2023-04-12 23:10:42 -07:00
.nvmrc Update to Node 16, update typescript, transpile to ES2022 (#317) 2023-10-17 21:33:18 -07:00
.prettierignore Add API Extractor for better visibility of API changes (#262) 2023-03-22 13:00:28 -07:00
.prettierrc.json5 Configure Renovate 2022-07-21 14:57:58 -07:00
CODE_OF_CONDUCT.md adding MS stuff 2020-05-22 15:13:43 -07:00
LICENSE adding MS stuff 2020-05-22 15:13:43 -07:00
README.md Update readmes 2022-09-15 15:22:05 -07:00
SECURITY.md adding MS stuff 2020-05-22 15:13:43 -07:00
beachball.config.js beachball sync 2023-05-16 18:24:08 -07:00
lage.config.js Add API Extractor for better visibility of API changes (#262) 2023-03-22 13:00:28 -07:00
package.json Update devDependency gh-pages to v6 (#322) 2023-10-18 04:57:45 +00:00
renovate.json5 Update to Node 16, update typescript, transpile to ES2022 (#317) 2023-10-17 21:33:18 -07:00
typedoc.json Convert to monorepo (#178) 2022-09-14 16:26:15 -07:00
yarn.lock Update devDependency gh-pages to v6 (#322) 2023-10-18 04:57:45 +00:00

README.md

workspace-tools monorepo

Please see the workspace-tools README for more information.

Contributing

This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.opensource.microsoft.com.

When you submit a pull request, a CLA bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., status check, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.

This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.