FluidFramework/pnpm-workspace.yaml

# This is the workspace definition for the client release group. See https://pnpm.io/pnpm-workspace_yaml for more
# information about the format.
#
# Guidelines for updating this file:
#
# 1. Keep the entries alphabetical wherever possible.
# 2. Be careful when using globs that end with "**". E.g. "packages/**". Doing so can include unexpected packages. This
#    is especially true of packages for which we build ESM and CJS. Such packages sometimes have package.json files in
#    their source or output directories during compilation.

packages:
  - "azure/packages/**"
  - "examples/**"
  - "experimental/**"
  - "packages/**"
  - "tools/markdown-magic"

  # exclude any package.json files that are inside src or output directories
  - "!**/dist/**"
  - "!**/lib/**"
  - "!**/src/**"
build: Narrow workspace definitions (#19047) Our workspace definitions are including projects that shouldn't be included, especially when using temporary package.json files to control the compilation of ESM/CJS in dual-emit packages. This change updates the definitions to be narrower. For the client workspace in particular, the results are more verbose because we have packages at arbitrary depths in the tree. We should address this over time by reorganizing the repo. For the server-related release groups the change is much smaller because they're small and follow conventions. 2024-01-04 05:45:45 +03:00			`# This is the workspace definition for the client release group. See https://pnpm.io/pnpm-workspace_yaml for more`
			`# information about the format.`
			`#`
			`# Guidelines for updating this file:`
			`#`
			`# 1. Keep the entries alphabetical wherever possible.`
			`# 2. Be careful when using globs that end with "". E.g. "packages/". Doing so can include unexpected packages. This`
			`# is especially true of packages for which we build ESM and CJS. Such packages sometimes have package.json files in`
			`# their source or output directories during compilation.`

build(client): Use pnpm in client release group (#13554) This PR changes the client release group to use pnpm instead of npm. lerna now uses the pnpm workspace config and uses pnpm to execute scripts. ## Things that should still work Note: `fluid-build` === `npm run build:fast` - fluid-build should continue to build the repo incrementally. - `fluid-build --install` should use pnpm for the release groups that use it and npm elsewhere. - You can still use npm to run scripts, e.g. `npm run build`, or you can switch to pnpm e.g. `pnpm build`. Co-authored-by: Rishhi Balakrishnan <107130183+RishhiB@users.noreply.github.com> 2023-01-26 01:36:03 +03:00			`packages:`
build: Update shared prettier config (#15758) Makes the following changes to our shared prettier config: 1. Formats YAML files with 2 spaces always and forces spaces since tabs are frowned upon in YAML. 2. ~~Formats markdown paragraphs to a single line, since GitHub is inconsistent in how it treats soft line breaks. More markdown formatting will need to be done with a different tool like markdownlint because prettier's markdown formatting isn't great.~~ 3. Treats some additional files as JSON5. 2023-06-05 22:37:40 +03:00			`- "azure/packages/**"`
			`- "examples/**"`
			`- "experimental/**"`
			`- "packages/**"`
build(client): Include markdown-magic and changelog-generator-wrapper in client release group (#21393) The markdown-magic and changelog-generator-wrapper packages are both private packages that we use in various places within the repo. We have been using `file:` links to these packages in the root workspace, but that causes `pnpm i` to always trigger resolution, which not only wastes time, but produces unnecessary lockfile changes in some cases. I left the markdown-magic package where it is to minimize the change, since it has a build pipeline and we continue to use `file:` dependencies in other places like docs. changelog-generator-wrapper, on the other hand, was moved to packages/tools. We can do the same for markdown-magic once its build pipeline is disabled/removed. Including these packages in the root workspace caused the following changes: - Some dependency versions were changed to match those used in the client release group. - The version of the packages was updated to match the client release group version. These packages are not published so the version should be irrelevant. 2024-06-25 05:21:20 +03:00			`- "tools/markdown-magic"`
build: Narrow workspace definitions (#19047) Our workspace definitions are including projects that shouldn't be included, especially when using temporary package.json files to control the compilation of ESM/CJS in dual-emit packages. This change updates the definitions to be narrower. For the client workspace in particular, the results are more verbose because we have packages at arbitrary depths in the tree. We should address this over time by reorganizing the repo. For the server-related release groups the change is much smaller because they're small and follow conventions. 2024-01-04 05:45:45 +03:00
			`# exclude any package.json files that are inside src or output directories`
			`- "!/dist/"`
			`- "!/lib/"`
			`- "!/src/"`