enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2025-01-07 09:06:22 +03:00
Code Issues Projects Releases Wiki Activity
afe4203f6a
enso/pnpm-lock.yaml

15408 lines
499 KiB
YAML
Raw Normal View History

Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
lockfileVersion: '9.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
settings:
autoInstallPeers: true
excludeLinksFromLockfile: false
overrides:
tslib: ^2.6.3
jsdom: ^24.1.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react': ^18.0.27
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws: ^8.18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
packageExtensionsChecksum: d5d1f1febc9b02d190bb3faf586ac1bb
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
pnpmfileChecksum: yrev2pk43cjl5fkasomnhoqkcu
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
importers:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
.:
dependencies:
tslib:
specifier: ^2.6.3
version: 2.6.3
typescript:
specifier: ^5.5.3
version: 5.5.3
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint/js':
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
specifier: ^9.13.0
version: 9.13.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/eslint-plugin':
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
specifier: ^8.10.0
Metadata should not depend on absolute text spans (#11390) close #11304 Changelog: - update: add `ide.snapshot` optional metadata field containing the source code of the file - update: `syncFileContents` method tries to repair the metadata spans when it detects that the source file was edited and the received code does not match the code stored in the `ide.snapshot` metadata field # Important Notes Tested in gui
2024-10-28 12:41:46 +03:00
version: 8.11.0(@typescript-eslint/parser@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3))(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/parser':
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
specifier: ^8.10.0
Metadata should not depend on absolute text spans (#11390) close #11304 Changelog: - update: add `ide.snapshot` optional metadata field containing the source code of the file - update: `syncFileContents` method tries to repair the metadata spans when it detects that the source file was edited and the received code does not match the code stored in the `ide.snapshot` metadata field # Important Notes Tested in gui
2024-10-28 12:41:46 +03:00
version: 8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/eslint-config-typescript':
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
specifier: ^14.1.1
Metadata should not depend on absolute text spans (#11390) close #11304 Changelog: - update: add `ide.snapshot` optional metadata field containing the source code of the file - update: `syncFileContents` method tries to repair the metadata spans when it detects that the source file was edited and the received code does not match the code stored in the `ide.snapshot` metadata field # Important Notes Tested in gui
2024-10-28 12:41:46 +03:00
version: 14.1.3(@typescript-eslint/parser@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3))(eslint-plugin-vue@9.29.1(eslint@9.13.0(jiti@1.21.6)))(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
specifier: ^9.13.0
version: 9.13.0(jiti@1.21.6)
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
eslint-plugin-jsdoc:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
specifier: ^50.4.3
version: 50.4.3(eslint@9.13.0(jiti@1.21.6))
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint-plugin-prettier:
specifier: ^5.2.1
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
version: 5.2.1(@types/eslint@8.56.10)(eslint-config-prettier@9.1.0(eslint@9.13.0(jiti@1.21.6)))(eslint@9.13.0(jiti@1.21.6))(prettier@3.3.2)
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint-plugin-react:
specifier: ^7.37.1
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
version: 7.37.1(eslint@9.13.0(jiti@1.21.6))
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
eslint-plugin-react-compiler:
specifier: 19.0.0-beta-8a03594-20241020
version: 19.0.0-beta-8a03594-20241020(eslint@9.13.0(jiti@1.21.6))
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
eslint-plugin-react-hooks:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
specifier: ^5.0.0
version: 5.0.0(eslint@9.13.0(jiti@1.21.6))
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint-plugin-vue:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
specifier: ^9.29.1
version: 9.29.1(eslint@9.13.0(jiti@1.21.6))
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
globals:
specifier: ^15.8.0
version: 15.8.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
npm-run-all:
specifier: ^4.1.5
version: 4.1.5
prettier:
specifier: ^3.3.2
version: 3.3.2
Edit prettier config (#10648)
2024-07-24 11:47:05 +03:00
prettier-plugin-organize-imports:
specifier: ^4.0.0
version: 4.0.0(prettier@3.3.2)(typescript@5.5.3)(vue-tsc@2.0.24(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
app/common:
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/query-core':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: 5.54.1
version: 5.54.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/query-persist-client-core':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^5.54.0
version: 5.54.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/vue-query':
specifier: '>= 5.54.0 < 5.56.0'
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
version: 5.54.2(vue@3.5.2(typescript@5.5.3))
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
idb-keyval:
specifier: ^6.2.1
version: 6.2.1
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
lib0:
specifier: ^0.2.85
version: 0.2.94
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
react:
specifier: ^18.3.1
version: 18.3.1
vitest:
specifier: ^1.3.1
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1)
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
vue:
specifier: ^3.5.2
version: 3.5.2(typescript@5.5.3)
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
app/gui:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/client-side-row-model':
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
specifier: ^31.1.1
version: 31.3.4
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/core':
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
specifier: ^31.1.1
version: 31.3.4
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/styles':
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
specifier: ^31.1.1
version: 31.3.4
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-enterprise/core':
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
specifier: ^31.1.1
version: 31.3.4
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-enterprise/range-selection':
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
specifier: ^31.1.1
version: 31.3.4
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-amplify/auth':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: 5.6.5
version: 5.6.5
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-amplify/core':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: 5.8.5
version: 5.8.5
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/parser':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^7.24.7
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
version: 7.25.6
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/commands':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^6.6.0
version: 6.6.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/lang-markdown':
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
specifier: ^v6.3.0
version: 6.3.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/language':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^6.10.2
version: 6.10.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/lint':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^6.8.1
version: 6.8.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/search':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^6.5.6
version: 6.5.6
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/state':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^6.4.1
version: 6.4.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/view':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^6.28.3
version: 6.28.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@fast-check/vitest':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^0.0.8
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 0.0.8(vitest@1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/vue':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.0.6
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
version: 1.1.0(vue@3.5.2(typescript@5.5.3))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@hookform/resolvers':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^3.4.0
version: 3.6.0(react-hook-form@7.52.0(react@18.3.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^3.5.5
version: 3.5.5
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/link':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^0.16.0
version: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/plain-text':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^0.16.0
version: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/utils':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^0.16.0
version: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.1.0
version: 1.2.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/highlight':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.1.6
version: 1.2.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@monaco-editor/react':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: 4.6.0
version: 4.6.0(monaco-editor@0.48.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@noble/hashes':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^1.4.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
version: 1.4.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/interactions':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^3.22.3
version: 3.22.3(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/react':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^7.74.0
version: 7.118.0(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@stripe/react-stripe-js':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^2.7.1
version: 2.7.2(@stripe/stripe-js@3.5.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@stripe/stripe-js':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^3.5.0
version: 3.5.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/react-query':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: 5.55.0
version: 5.55.0(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/vue-query':
specifier: '>= 5.54.0 < 5.56.0'
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
version: 5.54.2(vue@3.5.2(typescript@5.5.3))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vueuse/core':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^10.4.1
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
version: 10.11.0(vue@3.5.2(typescript@5.5.3))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vueuse/gesture':
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
specifier: ^2.0.0
version: 2.0.0(vue@3.5.2(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ag-grid-community:
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
specifier: ^31.1.1
version: 31.3.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ag-grid-enterprise:
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
specifier: ^31.1.1
version: 31.3.4
Table Editor Widget (#10774) Fixes #10293 The Table Editor Widget allows adding rows and columns, editing cells and renaming columns. [Screencast from 2024-08-07 13-17-37.webm](https://github.com/user-attachments/assets/d2e708b5-6516-4107-bc17-f018e455c111) # Important Notes * The parts of Table Visualization which were useful for the widget were put in vue component. On this occasion, we use aggrid vue.
2024-08-12 17:45:58 +03:00
ag-grid-vue3:
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
specifier: ^31.1.1
version: 31.3.4(typescript@5.5.3)
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
ajv:
specifier: ^8.12.0
version: 8.16.0
amazon-cognito-identity-js:
specifier: 6.3.6
version: 6.3.6
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
babel-plugin-react-compiler:
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
specifier: 19.0.0-beta-6fc168f-20241025
version: 19.0.0-beta-6fc168f-20241025
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
clsx:
specifier: ^2.1.1
version: 2.1.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
codemirror:
specifier: ^6.0.1
version: 6.0.1(@lezer/common@1.2.1)
culori:
specifier: ^3.2.0
version: 3.3.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
enso-common:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: workspace:*
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
version: link:../common
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
events:
specifier: ^3.3.0
version: 3.3.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
framer-motion:
specifier: 11.3.0
version: 11.3.0(@emotion/is-prop-valid@1.3.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hash-sum:
specifier: ^2.0.0
version: 2.0.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
input-otp:
specifier: 1.2.4
version: 1.2.4(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
install:
specifier: ^0.13.0
version: 0.13.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
is-network-error:
specifier: ^1.0.1
version: 1.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isomorphic-ws:
specifier: ^5.0.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
version: 5.0.0(ws@8.18.0)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical:
specifier: ^0.16.0
version: 0.16.0
lib0:
specifier: ^0.2.85
version: 0.2.94
magic-string:
specifier: ^0.30.3
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
version: 0.30.11
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
marked:
specifier: 14.1.3
version: 14.1.3
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
monaco-editor:
specifier: 0.48.0
version: 0.48.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
murmurhash:
specifier: ^2.0.1
version: 2.0.1
postcss-inline-svg:
specifier: ^6.0.0
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
version: 6.0.0(postcss@8.4.45)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
postcss-nesting:
specifier: ^12.0.1
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
version: 12.1.5(postcss@8.4.45)
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
qrcode.react:
specifier: 3.1.0
version: 3.1.0(react@18.3.1)
react:
specifier: ^18.3.1
version: 18.3.1
react-aria:
specifier: ^3.34.3
version: 3.34.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
react-aria-components:
specifier: ^1.3.3
version: 1.3.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
react-compiler-runtime:
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
specifier: 19.0.0-beta-6fc168f-20241025
version: 19.0.0-beta-6fc168f-20241025(react@18.3.1)
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
react-dom:
specifier: ^18.3.1
version: 18.3.1(react@18.3.1)
react-error-boundary:
specifier: 4.0.13
version: 4.0.13(react@18.3.1)
react-hook-form:
specifier: ^7.51.4
version: 7.52.0(react@18.3.1)
react-router:
specifier: ^6.23.1
version: 6.24.0(react@18.3.1)
react-router-dom:
specifier: ^6.23.1
version: 6.24.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
react-stately:
specifier: ^3.32.2
version: 3.32.2(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-toastify:
specifier: ^9.1.3
version: 9.1.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
sucrase:
specifier: ^3.34.0
version: 3.35.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
tailwind-merge:
specifier: ^2.3.0
version: 2.3.0
tailwind-variants:
specifier: 0.2.1
version: 0.2.1(tailwindcss@3.4.4)
tiny-invariant:
specifier: ^1.3.3
version: 1.3.3
ts-results:
specifier: ^3.3.0
version: 3.3.0
validator:
specifier: ^13.12.0
version: 13.12.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
veaury:
specifier: ^2.3.18
version: 2.4.1(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
vue:
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
specifier: ^3.5.2
version: 3.5.2(typescript@5.5.3)
Table Editor Widget (#10774) Fixes #10293 The Table Editor Widget allows adding rows and columns, editing cells and renaming columns. [Screencast from 2024-08-07 13-17-37.webm](https://github.com/user-attachments/assets/d2e708b5-6516-4107-bc17-f018e455c111) # Important Notes * The parts of Table Visualization which were useful for the widget were put in vue component. On this occasion, we use aggrid vue.
2024-08-12 17:45:58 +03:00
vue-component-type-helpers:
specifier: ^2.0.29
More robust ydoc server watch (#10817) Fixed occasional issues with ydoc server starting in dev mode, which were caused by missing dist file, then nodemon failing to trigger a file watch event after esbuild completion. Now esbuild is directly responsible for managing a child process, without needing an additional layer of file watchers.
2024-08-14 16:17:53 +03:00
version: 2.0.29
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
y-protocols:
specifier: ^1.0.5
version: 1.0.6(yjs@13.6.18)
y-textarea:
specifier: ^1.0.0
version: 1.0.1(yjs@13.6.18)
y-websocket:
specifier: ^1.5.0
version: 1.5.4(yjs@13.6.18)
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ydoc-shared:
specifier: workspace:*
version: link:../ydoc-shared
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yjs:
specifier: ^13.6.7
version: 13.6.18
zod:
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^3.23.8
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
version: 3.23.8
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
zustand:
specifier: ^4.5.4
version: 4.5.4(@types/react@18.3.3)(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/theme-one-dark':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^6.1.2
version: 6.1.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@danmarshall/deckgl-typings':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^4.9.28
version: 4.9.28
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/plugin-vue':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^0.17.12
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 0.17.17(histoire@0.17.17(@types/node@22.9.0)(lightningcss@1.25.1)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)))(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))(vue@3.5.2(typescript@5.5.3))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@modyfi/vite-plugin-yaml':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^1.0.4
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 1.1.0(rollup@4.24.0)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@open-rpc/server-js':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.9.4
version: 1.9.5
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@playwright/test':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.40.0
version: 1.45.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^3.22.1
Align esbuild versions across packages (#11459) Part of #11458 Should get rid of the "magical" CI failure: https://github.com/enso-org/enso/actions/runs/11576387008/job/32225209090#step:7:254
2024-11-06 02:43:27 +03:00
version: 3.25.0(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/react-query-devtools':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: 5.45.1
version: 5.45.1(@tanstack/react-query@5.55.0(react@18.3.1))(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tsconfig/node20':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^20.1.4
version: 20.1.4
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/css.escape':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.5.2
version: 1.5.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/culori':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^2.0.1
version: 2.1.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^7.4.0
version: 7.4.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/hash-sum':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.0.0
version: 1.0.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/jsdom':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^21.1.1
version: 21.1.7
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/mapbox-gl':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^2.7.13
version: 2.7.21
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node':
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
specifier: ^22.9.0
version: 22.9.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^18.0.27
version: 18.3.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react-dom':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^18.0.10
version: 18.3.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/shuffle-seed':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.1.0
version: 1.1.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/tar':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: ^6.1.4
version: 6.1.13
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/validator':
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^13.11.7
version: 13.12.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/wicg-file-system-access':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^2023.10.2
version: 2023.10.5
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/ws':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^8.5.5
version: 8.5.10
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitejs/plugin-react':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
specifier: ^4.3.3
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 4.3.3(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitejs/plugin-vue':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^5.0.4
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 5.0.5(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))(vue@3.5.2(typescript@5.5.3))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/coverage-v8':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.3.1
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 1.6.0(vitest@1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/test-utils':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^2.4.6
version: 2.4.6
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/tsconfig':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^0.5.1
version: 0.5.1
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
chalk:
specifier: ^5.3.0
version: 5.3.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cross-env:
specifier: ^7.0.3
version: 7.0.3
css.escape:
specifier: ^1.5.1
version: 1.5.1
d3:
specifier: ^7.4.0
version: 7.9.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
fast-check:
specifier: ^3.15.0
version: 3.19.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
floating-vue:
specifier: ^2.0.0-beta.24
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
version: 2.0.0(vue@3.5.2(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hash-wasm:
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^4.11.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
version: 4.11.0
histoire:
specifier: ^0.17.2
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 0.17.17(@types/node@22.9.0)(lightningcss@1.25.1)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsdom:
specifier: ^24.1.0
version: 24.1.0
playwright:
specifier: ^1.39.0
version: 1.45.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
postcss:
specifier: ^8.4.29
version: 8.4.45
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prettier:
specifier: ^3.3.2
version: 3.3.2
prettier-plugin-organize-imports:
specifier: ^4.0.0
version: 4.0.0(prettier@3.3.2)(typescript@5.5.3)(vue-tsc@2.0.24(typescript@5.5.3))
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
prettier-plugin-tailwindcss:
specifier: ^0.5.11
Optimize asset table rendering (#11382) - Depends on: - #11380 - Some optimizations for re-rendering assets table: - Omit `visibilities` from `state` in favor of passing each `AssetRow`'s `visibility` directly to the row. This minimizes spurious `state` updates. - Pass `id` and `parentId` to `AssetRow` instead of the entire object. This ensures that re-fetches do not force a re-render of the `AssetRow` - we are no longer passing a reference to the object, so we are now comparing by string comparison (which is almost always stable). # Important Notes None
2024-10-31 13:36:10 +03:00
version: 0.5.14(@ianvs/prettier-plugin-sort-imports@4.3.0(prettier@3.3.2))(prettier-plugin-organize-imports@4.0.0(prettier@3.3.2)(typescript@5.5.3)(vue-tsc@2.0.24(typescript@5.5.3)))(prettier@3.3.2)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
shuffle-seed:
specifier: ^1.1.6
version: 1.1.6
sql-formatter:
specifier: ^13.0.0
version: 13.1.0
tailwindcss:
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
specifier: ^3.4.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
version: 3.4.4
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
tailwindcss-animate:
specifier: 1.0.7
version: 1.0.7(tailwindcss@3.4.4)
tailwindcss-react-aria-components:
specifier: ^1.1.1
version: 1.1.3(tailwindcss@3.4.4)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tar:
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: ^6.2.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
version: 6.2.1
tsx:
specifier: ^4.7.1
version: 4.16.0
typescript:
specifier: ^5.5.3
version: 5.5.3
vite:
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
specifier: ^5.4.10
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vite-plugin-vue-devtools:
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
specifier: 7.6.3
version: 7.6.3(rollup@4.24.0)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))(vue@3.5.2(typescript@5.5.3))
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
vite-plugin-wasm:
specifier: ^3.3.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 3.3.0(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vitest:
specifier: ^1.3.1
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vue-react-wrapper:
specifier: ^0.3.1
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
version: 0.3.1(vue@3.5.2(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vue-tsc:
specifier: ^2.0.24
version: 2.0.24(typescript@5.5.3)
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
yaml:
specifier: ^2.4.5
version: 2.4.5
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ydoc-server:
specifier: workspace:*
version: link:../ydoc-server
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
app/ide-desktop/client:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
chalk:
specifier: ^5.2.0
version: 5.3.0
create-servers:
specifier: 3.2.0
version: 3.2.0
electron-is-dev:
specifier: ^2.0.0
version: 2.0.0
mime-types:
specifier: ^2.1.35
version: 2.1.35
mkcert:
specifier: 3.2.0
version: 3.2.0
opener:
specifier: ^1.5.2
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
version: 1.5.2
semver:
specifier: ^7.6.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
version: 7.6.3
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
string-length:
specifier: ^5.0.1
version: 5.0.1
tar:
specifier: ^6.2.0
version: 6.2.1
yargs:
specifier: 17.6.2
version: 17.6.2
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ydoc-server:
specifier: workspace:*
version: link:../../ydoc-server
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-syntax-import-attributes':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: ^7.24.7
Setup Screen Improvements (#10844)
2024-09-05 19:11:02 +03:00
version: 7.24.7(@babel/core@7.25.2)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/notarize':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: 2.1.0
version: 2.1.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@playwright/test':
Integration Tests (#11186) A stub for integration tests to be run locally; part of #8487 To run tests, you need to: 1. Build IDE package: `./run ide build` 2. set ENSO_TEST_USER and ENSO_TEST_USER_PASSWORD to some working credentials (I used my personal account, but there will be also test user soon) 3. run `corepack pnpm -r --filter enso exec playwright test` The tests are run with a separate projects directory set up in tmpdir, so any local workspace dir is not affected. The only test so far just checks if it's possible to log in and create a new project.
2024-09-27 18:11:13 +03:00
specifier: ^1.45.0
version: 1.45.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/mime-types':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: ^2.1.1
version: 2.1.4
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node':
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
specifier: ^22.9.0
version: 22.9.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/opener':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: ^1.4.0
version: 1.4.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/semver':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: ^7.5.8
version: 7.5.8
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/tar':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: ^6.1.4
version: 6.1.13
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/yargs':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: ^17.0.30
version: 17.0.32
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
babel-plugin-react-compiler:
specifier: 19.0.0-beta-6fc168f-20241025
version: 19.0.0-beta-6fc168f-20241025
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
cross-env:
specifier: ^7.0.3
version: 7.0.3
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
electron:
specifier: 31.2.0
version: 31.2.0
electron-builder:
specifier: ^24.13.3
Optimize asset table rendering (#11382) - Depends on: - #11380 - Some optimizations for re-rendering assets table: - Omit `visibilities` from `state` in favor of passing each `AssetRow`'s `visibility` directly to the row. This minimizes spurious `state` updates. - Pass `id` and `parentId` to `AssetRow` instead of the entire object. This ensures that re-fetches do not force a re-render of the `AssetRow` - we are no longer passing a reference to the object, so we are now comparing by string comparison (which is almost always stable). # Important Notes None
2024-10-31 13:36:10 +03:00
version: 24.13.3(electron-builder-squirrel-windows@24.13.3(dmg-builder@24.13.3))
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
enso-common:
specifier: workspace:*
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
version: link:../../common
enso-gui:
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
specifier: workspace:*
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
version: link:../../gui
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
enso-runner:
specifier: workspace:*
version: link:../../../lib/js/runner
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esbuild:
Align esbuild versions across packages (#11459) Part of #11458 Should get rid of the "magical" CI failure: https://github.com/enso-org/enso/actions/runs/11576387008/job/32225209090#step:7:254
2024-11-06 02:43:27 +03:00
specifier: ^0.23.0
version: 0.23.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esbuild-plugin-wasm:
specifier: ^1.1.0
version: 1.1.0
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
fast-glob:
specifier: ^3.2.12
version: 3.3.2
Integration Tests (#11186) A stub for integration tests to be run locally; part of #8487 To run tests, you need to: 1. Build IDE package: `./run ide build` 2. set ENSO_TEST_USER and ENSO_TEST_USER_PASSWORD to some working credentials (I used my personal account, but there will be also test user soon) 3. run `corepack pnpm -r --filter enso exec playwright test` The tests are run with a separate projects directory set up in tmpdir, so any local workspace dir is not affected. The only test so far just checks if it's possible to log in and create a new project.
2024-09-27 18:11:13 +03:00
playwright:
specifier: ^1.45.0
version: 1.45.0
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
portfinder:
specifier: ^1.0.32
version: 1.0.32
tsx:
specifier: ^4.7.1
version: 4.16.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vite:
Increase timeout and vite version (#11492) 1. The electron test hit timeouts from time to time, probably because of slow response from the engine: increased timeout. 2. Unify vite version across packages.
2024-11-08 11:43:02 +03:00
specifier: ^5.4.10
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
app/ide-desktop/icons:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/sharp':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^0.31.1
version: 0.31.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/to-ico':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
specifier: ^1.1.1
version: 1.1.3
sharp:
specifier: ^0.31.2
version: 0.31.3
to-ico:
specifier: ^1.1.5
version: 1.1.5
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
app/rust-ffi: {}
app/ydoc-server:
dependencies:
debug:
specifier: ^4.3.6
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
version: 4.3.7
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
fast-diff:
specifier: ^1.3.0
version: 1.3.0
isomorphic-ws:
specifier: ^5.0.0
version: 5.0.0(ws@8.18.0)
lib0:
specifier: ^0.2.85
version: 0.2.94
y-protocols:
specifier: ^1.0.5
version: 1.0.6(yjs@13.6.18)
ydoc-shared:
specifier: workspace:*
version: link:../ydoc-shared
yjs:
specifier: ^13.6.7
version: 13.6.18
zod:
specifier: ^3.23.8
version: 3.23.8
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@fast-check/vitest':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^0.0.8
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 0.0.8(vitest@1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/debug':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^4.1.12
version: 4.1.12
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node':
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
specifier: ^22.9.0
version: 22.9.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
typescript:
specifier: ^5.5.3
version: 5.5.3
vite-plugin-wasm:
specifier: ^3.3.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 3.3.0(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
vitest:
specifier: ^1.3.1
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1)
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
app/ydoc-server-nodejs:
dependencies:
ydoc-server:
specifier: workspace:*
version: link:../ydoc-server
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node':
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
specifier: ^22.9.0
version: 22.9.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esbuild:
specifier: ^0.23.0
version: 0.23.0
esbuild-plugin-wasm:
specifier: ^1.1.0
version: 1.1.0
typescript:
specifier: ^5.5.3
version: 5.5.3
app/ydoc-server-polyglot:
dependencies:
ydoc-server:
specifier: workspace:*
version: link:../ydoc-server
ydoc-shared:
specifier: workspace:*
version: link:../ydoc-shared
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@fal-works/esbuild-plugin-global-externals':
Add compression to the metadata code snapshot (#11470) close #11420 Changelog: - update: add zlib compression to the `snapshot` metadata field - add: implement nodejs `zlib` for polyglot ydoc-server - add: implement nodejs `Buffer` for polyglot ydoc-server
2024-11-05 14:57:43 +03:00
specifier: ^2.1.2
version: 2.1.2
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esbuild:
specifier: ^0.23.0
version: 0.23.0
esbuild-plugin-wasm:
specifier: ^1.1.0
version: 1.1.0
typescript:
specifier: ^5.5.3
version: 5.5.3
app/ydoc-shared:
dependencies:
Render tables in documentation. (#11564) * Render tables in documentation. Also: - Separate parser for our flavor of Markdown from the CodeMirror integration; move the parser into ydoc-shared and use for Markdown line-wrapping. - Introduce our own version of yCollab extension; initially just the upstream version translated to Typescript and our code style. - Refactor CodeEditor. * CHANGELOG, prettier * Apply @farmaazon review. * Fix * Lint * Cleanup * Integration tests for GraphNodeComment Also a little refactoring in preparation for new implementation. * Workaround stuck CI * Revert "Workaround stuck CI" This reverts commit 74313842baa15d12c1a8be0529a16aa8ea204d83. * Fix merge --------- Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2024-11-20 13:40:24 +03:00
'@lezer/common':
specifier: ^1.1.0
version: 1.2.1
'@lezer/markdown':
specifier: ^1.3.1
version: 1.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@noble/hashes':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^1.4.0
version: 1.4.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@open-rpc/client-js':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^1.8.1
version: 1.8.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/debug':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^4.1.12
version: 4.1.12
change-case:
specifier: ^4.1.2
version: 4.1.2
debug:
specifier: ^4.3.6
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
version: 4.3.7
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
enso-common:
specifier: workspace:*
version: link:../common
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
fast-diff:
specifier: ^1.3.0
version: 1.3.0
hash-wasm:
specifier: ^4.11.0
version: 4.11.0
isomorphic-ws:
specifier: ^5.0.0
version: 5.0.0(ws@8.18.0)
lib0:
specifier: ^0.2.85
version: 0.2.94
partysocket:
specifier: ^1.0.1
version: 1.0.1
rimraf:
specifier: ^6.0.1
version: 6.0.1
rust-ffi:
specifier: workspace:*
version: link:../rust-ffi
yjs:
specifier: ^13.6.7
version: 13.6.18
zod:
specifier: ^3.23.8
version: 3.23.8
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@fast-check/vitest':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^0.0.8
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 0.0.8(vitest@1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tsconfig/node20':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
specifier: ^20.1.4
version: 20.1.4
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node':
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
specifier: ^22.9.0
version: 22.9.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
typescript:
specifier: ^5.5.3
version: 5.5.3
vite-node:
specifier: ^2.0.4
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 2.0.4(@types/node@22.9.0)(lightningcss@1.25.1)
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
vite-plugin-wasm:
specifier: ^3.3.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 3.3.0(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
vitest:
specifier: ^1.3.1
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
version: 1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1)
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lib/js/runner:
dependencies:
spectorjs:
specifier: ^0.9.27
version: 0.9.30
devDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node':
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
specifier: ^22.9.0
version: 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
typescript:
specifier: ^5.5.3
version: 5.5.3
packages:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
7zip-bin@5.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ukTPVhqG4jNzMro2qA9HSCSSVJN3aN7tlb+hfqYCt3ER0yWroeA2VR38MNrOHLQ/cVj+DaIMad0kFCtWWowh/A==}
'@ag-grid-community/client-side-row-model@31.3.4':
resolution: {integrity: sha512-lbrbhwSoY1/N2CiOQBa322gVnrhyrbzyG7cvbOef3itAiaLUzQ03PWBw09d9mj+/0hnqMs386ZuGX15FWJaTqQ==}
'@ag-grid-community/core@31.3.4':
resolution: {integrity: sha512-Fz7P4lMAYDo9rG6jOA8OXlAXta/4E+PiCdjT7M9OloaXAJtU47oO4f3VKV7rdbVCC8SGSo0cBCateddQTAFCNQ==}
'@ag-grid-community/styles@31.3.4':
resolution: {integrity: sha512-5pgt/Qq/GxiJi59UA17ltG5U4r0J+GB3S/QCysJFi6kmgmCDsbCfisekTwSh0xxOGO+OIhejoqsOuEnTcw78kg==}
'@ag-grid-enterprise/core@31.3.4':
resolution: {integrity: sha512-9zjxVNih+gW3bU2aufcTjwUh2XzlYkts5kE4S7CTDIo3Dke9iaeg4KlyskprGiZjYmJMroxkl9CSWUGUUAN1rQ==}
'@ag-grid-enterprise/range-selection@31.3.4':
resolution: {integrity: sha512-XSpGAeNP3TufydW7nE2K5cyNVX1O0Ye/8WbZU5cN3mbyjpzUQlO3RQl/iIw5YqlTRfUN4Ll6AUDC4vMj4SzQDA==}
'@akryum/tinypool@0.3.1':
resolution: {integrity: sha512-nznEC1ZA/m3hQDEnrGQ4c5gkaa9pcaVnw4LFJyzBAaR7E3nfiAPEHS3otnSafpZouVnoKeITl5D+2LsnwlnK8g==}
engines: {node: '>=14.0.0'}
'@alloc/quick-lru@5.2.0':
resolution: {integrity: sha512-UrcABB+4bUrFABwbluTIBErXwvbsU/V7TZWfmbgJfbkwiBuziS9gxdODUyuiecfdGQ85jglMW6juS3+z5TsKLw==}
engines: {node: '>=10'}
'@ampproject/remapping@2.3.0':
resolution: {integrity: sha512-30iZtAPgz+LTIYoeivqYo853f02jBYSd5uGnGpkFV0M3xOt9aN73erkgYAmZU43x4VfqcnLxW9Kpg3R5LC4YYw==}
engines: {node: '>=6.0.0'}
'@antfu/utils@0.7.10':
resolution: {integrity: sha512-+562v9k4aI80m1+VuMHehNJWLOFjBnXn3tdOitzD0il5b7smkSBal4+a3oKiQTbrwMmN/TBUMDvbdoWDehgOww==}
'@aws-amplify/auth@5.6.5':
resolution: {integrity: sha512-NkBbYe3kV4LXj/VBeh0/HTZCNjhs8gB1frfJ2r1ZG3j+Q3taeKV4jhZcM1SyRbFh5ZGHiVSJPVefgBPi7UXBrw==}
'@aws-amplify/core@5.8.5':
resolution: {integrity: sha512-R7zB+VUyNRT/7GCfBfWOIz2vy70VbHNfhotbdyo02ZVcc4vyXt+tsdZvvMSm1SB5uQ411jiAfDmTvOzLOIaJsA==}
'@aws-crypto/ie11-detection@1.0.0':
resolution: {integrity: sha512-kCKVhCF1oDxFYgQrxXmIrS5oaWulkvRcPz+QBDMsUr2crbF4VGgGT6+uQhSwJFdUAQ2A//Vq+uT83eJrkzFgXA==}
'@aws-crypto/sha256-browser@1.2.2':
resolution: {integrity: sha512-0tNR4kBtJp+9S0kis4+JLab3eg6QWuIeuPhzaYoYwNUXGBgsWIkktA2mnilet+EGWzf3n1zknJXC4X4DVyyXbg==}
'@aws-crypto/sha256-js@1.2.2':
resolution: {integrity: sha512-Nr1QJIbW/afYYGzYvrF70LtaHrIRtd4TNAglX8BvlfxJLZ45SAmueIKYl5tWoNBPzp65ymXGFK0Bb1vZUpuc9g==}
'@aws-crypto/sha256-js@5.2.0':
resolution: {integrity: sha512-FFQQyu7edu4ufvIZ+OadFpHHOt+eSTBaYaki44c+akjg7qZg9oOQeLlk77F6tSYqjDAFClrHJk9tMf0HdVyOvA==}
engines: {node: '>=16.0.0'}
'@aws-crypto/supports-web-crypto@1.0.0':
resolution: {integrity: sha512-IHLfv+WmVH89EW4n6a5eE8/hUlz6qkWGMn/v4r5ZgzcXdTC5nolii2z3k46y01hWRiC2PPhOdeSLzMUCUMco7g==}
'@aws-crypto/util@1.2.2':
resolution: {integrity: sha512-H8PjG5WJ4wz0UXAFXeJjWCW1vkvIJ3qUUD+rGRwJ2/hj+xT58Qle2MTql/2MGzkU+1JLAFuR6aJpLAjHwhmwwg==}
'@aws-crypto/util@5.2.0':
resolution: {integrity: sha512-4RkU9EsI6ZpBve5fseQlGNUWKMa1RLPQ1dnjnQoe07ldfIzcsGb5hC5W0Dm7u423KWzawlrpbjXBrXCEv9zazQ==}
'@aws-sdk/abort-controller@3.6.1':
resolution: {integrity: sha512-X81XkxX/2Tvv9YNcEto/rcQzPIdKJHFSnl9hBl/qkSdCFV/GaQ2XNWfKm5qFXMLlZNFS0Fn5CnBJ83qnBm47vg==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/client-cloudwatch-logs@3.6.1':
resolution: {integrity: sha512-QOxIDnlVTpnwJ26Gap6RGz61cDLH6TKrIp30VqwdMeT1pCGy8mn9rWln6XA+ymkofHy/08RfpGp+VN4axwd4Lw==}
engines: {node: '>=10.0.0'}
'@aws-sdk/config-resolver@3.6.1':
resolution: {integrity: sha512-qjP1g3jLIm+XvOIJ4J7VmZRi87vsDmTRzIFePVeG+EFWwYQLxQjTGMdIj3yKTh1WuZ0HByf47mGcpiS4HZLm1Q==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/credential-provider-env@3.6.1':
resolution: {integrity: sha512-coeFf/HnhpGidcAN1i1NuFgyFB2M6DeN1zNVy4f6s4mAh96ftr9DgWM1CcE3C+cLHEdpNqleVgC/2VQpyzOBLQ==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/credential-provider-imds@3.6.1':
resolution: {integrity: sha512-bf4LMI418OYcQbyLZRAW8Q5AYM2IKrNqOnIcfrFn2f17ulG7TzoWW3WN/kMOw4TC9+y+vIlCWOv87GxU1yP0Bg==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/credential-provider-ini@3.6.1':
resolution: {integrity: sha512-3jguW6+ttRNddRZvbrs1yb3F1jrUbqyv0UfRoHuOGthjTt+L9sDpJaJGugYnT3bS9WBu1NydLVE2kDV++mJGVw==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/credential-provider-node@3.6.1':
resolution: {integrity: sha512-VAHOcsqkPrF1k/fA62pv9c75lUWe5bHpcbFX83C3EUPd2FXV10Lfkv6bdWhyZPQy0k8T+9/yikHH3c7ZQeFE5A==}
engines: {node: '>=10.0.0'}
'@aws-sdk/credential-provider-process@3.6.1':
resolution: {integrity: sha512-d0/TpMoEV4qMYkdpyyjU2Otse9X2jC1DuxWajHOWZYEw8oejMvXYTZ10hNaXZvAcNM9q214rp+k4mkt6gIcI6g==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/fetch-http-handler@3.6.1':
resolution: {integrity: sha512-N8l6ZbwhINuWG5hsl625lmIQmVjzsqRPmlgh061jm5D90IhsM5/3A3wUxpB/k0av1dmuMRw/m0YtBU5w4LOwvw==}
'@aws-sdk/hash-node@3.6.1':
resolution: {integrity: sha512-iKEpzpyaG9PYCnaOGwTIf0lffsF/TpsXrzAfnBlfeOU/3FbgniW2z/yq5xBbtMDtLobtOYC09kUFwDnDvuveSA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/invalid-dependency@3.6.1':
resolution: {integrity: sha512-d0RLqK7yeDCZJKopnGmGXo2rYkQNE7sGKVmBHQD1j1kKZ9lWwRoJeWqo834JNPZzY5XRvZG5SuIjJ1kFy8LpyQ==}
'@aws-sdk/is-array-buffer@3.6.1':
resolution: {integrity: sha512-qm2iDJmCrxlQE2dsFG+TujPe7jw4DF+4RTrsFMhk/e3lOl3MAzQ6Fc2kXtgeUcVrZVFTL8fQvXE1ByYyI6WbCw==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/middleware-content-length@3.6.1':
resolution: {integrity: sha512-QRcocG9f5YjYzbjs2HjKla6ZIjvx8Y8tm1ZSFOPey81m18CLif1O7M3AtJXvxn+0zeSck9StFdhz5gfjVNYtDg==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/middleware-host-header@3.6.1':
resolution: {integrity: sha512-nwq8R2fGBRZQE0Fr/jiOgqfppfiTQCUoD8hyX3qSS7Qc2uqpsDOt2TnnoZl56mpQYkF/344IvMAkp+ew6wR73w==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/middleware-logger@3.6.1':
resolution: {integrity: sha512-zxaSLpwKlja7JvK20UsDTxPqBZUo3rbDA1uv3VWwpxzOrEWSlVZYx/KLuyGWGkx9V71ZEkf6oOWWJIstS0wyQQ==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/middleware-retry@3.6.1':
resolution: {integrity: sha512-WHeo4d2jsXxBP+cec2SeLb0btYXwYXuE56WLmNt0RvJYmiBzytUeGJeRa9HuwV574kgigAuHGCeHlPO36G4Y0Q==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/middleware-serde@3.6.1':
resolution: {integrity: sha512-EdQCFZRERfP3uDuWcPNuaa2WUR3qL1WFDXafhcx+7ywQxagdYqBUWKFJlLYi6njbkOKXFM+eHBzoXGF0OV3MJA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/middleware-signing@3.6.1':
resolution: {integrity: sha512-1woKq+1sU3eausdl8BNdAMRZMkSYuy4mxhLsF0/qAUuLwo1eJLLUCOQp477tICawgu4O4q2OAyUHk7wMqYnQCg==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/middleware-stack@3.6.1':
resolution: {integrity: sha512-EPsIxMi8LtCt7YwTFpWGlVGYJc0q4kwFbOssY02qfqdCnyqi2y5wo089dH7OdxUooQ0D7CPsXM1zTTuzvm+9Fw==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/middleware-user-agent@3.6.1':
resolution: {integrity: sha512-YvXvwllNDVvxQ30vIqLsx+P6jjnfFEQUmhlv64n98gOme6h2BqoyQDcC3yHRGctuxRZEsR7W/H1ASTKC+iabbQ==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/node-config-provider@3.6.1':
resolution: {integrity: sha512-x2Z7lm0ZhHYqMybvkaI5hDKfBkaLaXhTDfgrLl9TmBZ3QHO4fIHgeL82VZ90Paol+OS+jdq2AheLmzbSxv3HrA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/node-http-handler@3.6.1':
resolution: {integrity: sha512-6XSaoqbm9ZF6T4UdBCcs/Gn2XclwBotkdjj46AxO+9vRAgZDP+lH/8WwZsvfqJhhRhS0qxWrks98WGJwmaTG8g==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/property-provider@3.6.1':
resolution: {integrity: sha512-2gR2DzDySXKFoj9iXLm1TZBVSvFIikEPJsbRmAZx5RBY+tp1IXWqZM6PESjaLdLg/ZtR0QhW2ZcRn0fyq2JfnQ==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/protocol-http@3.6.1':
resolution: {integrity: sha512-WkQz7ncVYTLvCidDfXWouDzqxgSNPZDz3Bql+7VhZeITnzAEcr4hNMyEqMAVYBVugGmkG2W6YiUqNNs1goOcDA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/querystring-builder@3.6.1':
resolution: {integrity: sha512-ESe255Yl6vB1AMNqaGSQow3TBYYnpw0AFjE40q2VyiNrkbaqKmW2EzjeCy3wEmB1IfJDHy3O12ZOMUMOnjFT8g==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/querystring-parser@3.6.1':
resolution: {integrity: sha512-hh6dhqamKrWWaDSuO2YULci0RGwJWygoy8hpCRxs/FpzzHIcbm6Cl6Jhrn5eKBzOBv+PhCcYwbfad0kIZZovcQ==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/service-error-classification@3.6.1':
resolution: {integrity: sha512-kZ7ZhbrN1f+vrSRkTJvXsu7BlOyZgym058nPA745+1RZ1Rtv4Ax8oknf2RvJyj/1qRUi8LBaAREjzQ3C8tmLBA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/shared-ini-file-loader@3.6.1':
resolution: {integrity: sha512-BnLHtsNLOoow6rPV+QVi6jnovU5g1m0YzoUG0BQYZ1ALyVlWVr0VvlUX30gMDfdYoPMp+DHvF8GXdMuGINq6kQ==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/signature-v4@3.6.1':
resolution: {integrity: sha512-EAR0qGVL4AgzodZv4t+BSuBfyOXhTNxDxom50IFI1MqidR9vI6avNZKcPHhgXbm7XVcsDGThZKbzQ2q7MZ2NTA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/smithy-client@3.6.1':
resolution: {integrity: sha512-AVpRK4/iUxNeDdAm8UqP0ZgtgJMQeWcagTylijwelhWXyXzHUReY1sgILsWcdWnoy6gq845W7K2VBhBleni8+w==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/types@3.598.0':
resolution: {integrity: sha512-742uRl6z7u0LFmZwDrFP6r1wlZcgVPw+/TilluDJmCAR8BgRw3IR+743kUXKBGd8QZDRW2n6v/PYsi/AWCDDMQ==}
engines: {node: '>=16.0.0'}
'@aws-sdk/types@3.6.1':
resolution: {integrity: sha512-4Dx3eRTrUHLxhFdLJL8zdNGzVsJfAxtxPYYGmIddUkO2Gj3WA1TGjdfG4XN/ClI6e1XonCHafQX3UYO/mgnH3g==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/url-parser-native@3.6.1':
resolution: {integrity: sha512-3O+ktsrJoE8YQCho9L41YXO8EWILXrSeES7amUaV3mgIV5w4S3SB/r4RkmylpqRpQF7Ry8LFiAnMqH1wa4WBPA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/url-parser@3.6.1':
resolution: {integrity: sha512-pWFIePDx0PMCleQRsQDWoDl17YiijOLj0ZobN39rQt+wv5PhLSZDz9PgJsqS48nZ6hqsKgipRcjiBMhn5NtFcQ==}
'@aws-sdk/util-base64-browser@3.6.1':
resolution: {integrity: sha512-+DHAIgt0AFARDVC7J0Z9FkSmJhBMlkYdOPeAAgO0WaQoKj7rtsLQJ7P3v3aS1paKN5/sk5xNY7ziVB6uHtOvHA==}
'@aws-sdk/util-base64-node@3.6.1':
resolution: {integrity: sha512-oiqzpsvtTSS92+cL3ykhGd7t3qBJKeHvrgOwUyEf1wFWHQ2DPJR+dIMy5rMFRXWLKCl3w7IddY2rJCkLYMjaqQ==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/util-body-length-browser@3.6.1':
resolution: {integrity: sha512-IdWwE3rm/CFDk2F+IwTZOFTnnNW5SB8y1lWiQ54cfc7y03hO6jmXNnpZGZ5goHhT+vf1oheNQt1J47m0pM/Irw==}
'@aws-sdk/util-body-length-node@3.6.1':
resolution: {integrity: sha512-CUG3gc18bSOsqViQhB3M4AlLpAWV47RE6yWJ6rLD0J6/rSuzbwbjzxM39q0YTAVuSo/ivdbij+G9c3QCirC+QQ==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/util-buffer-from@3.6.1':
resolution: {integrity: sha512-OGUh2B5NY4h7iRabqeZ+EgsrzE1LUmNFzMyhoZv0tO4NExyfQjxIYXLQQvydeOq9DJUbCw+yrRZrj8vXNDQG+g==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/util-hex-encoding@3.6.1':
resolution: {integrity: sha512-pzsGOHtU2eGca4NJgFg94lLaeXDOg8pcS9sVt4f9LmtUGbrqRveeyBv0XlkHeZW2n0IZBssPHipVYQFlk7iaRA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/util-locate-window@3.568.0':
resolution: {integrity: sha512-3nh4TINkXYr+H41QaPelCceEB2FXP3fxp93YZXB/kqJvX0U9j0N0Uk45gvsjmEPzG8XxkPEeLIfT2I1M7A6Lig==}
engines: {node: '>=16.0.0'}
'@aws-sdk/util-uri-escape@3.6.1':
resolution: {integrity: sha512-tgABiT71r0ScRJZ1pMX0xO0QPMMiISCtumph50IU5VDyZWYgeIxqkMhIcrL1lX0QbNCMgX0n6rZxGrrbjDNavA==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/util-user-agent-browser@3.6.1':
resolution: {integrity: sha512-KhJ4VED4QpuBVPXoTjb5LqspX1xHWJTuL8hbPrKfxj+cAaRRW2CNEe7PPy2CfuHtPzP3dU3urtGTachbwNb0jg==}
'@aws-sdk/util-user-agent-node@3.6.1':
resolution: {integrity: sha512-PWwL5EDRwhkXX40m5jjgttlBmLA7vDhHBen1Jcle0RPIDFRVPSE7GgvLF3y4r3SNH0WD6hxqadT50bHQynXW6w==}
engines: {node: '>= 10.0.0'}
'@aws-sdk/util-utf8-browser@3.259.0':
resolution: {integrity: sha512-UvFa/vR+e19XookZF8RzFZBrw2EUkQWxiBW0yYQAhvk3C+QVGl0H3ouca8LDBlBfQKXwmW3huo/59H8rwb1wJw==}
'@aws-sdk/util-utf8-browser@3.6.1':
resolution: {integrity: sha512-gZPySY6JU5gswnw3nGOEHl3tYE7vPKvtXGYoS2NRabfDKRejFvu+4/nNW6SSpoOxk6LSXsrWB39NO51k+G4PVA==}
'@aws-sdk/util-utf8-node@3.6.1':
resolution: {integrity: sha512-4s0vYfMUn74XLn13rUUhNsmuPMh0j1d4rF58wXtjlVUU78THxonnN8mbCLC48fI3fKDHTmDDkeEqy7+IWP9VyA==}
engines: {node: '>= 10.0.0'}
'@babel/code-frame@7.24.7':
resolution: {integrity: sha512-BcYH1CVJBO9tvyIZ2jVeXgSIMvGZ2FDRvDdOIVQyuklNKSsx+eppDEBq/g47Ayw+RqNFE+URvOShmf+f/qwAlA==}
engines: {node: '>=6.9.0'}
'@babel/compat-data@7.25.4':
resolution: {integrity: sha512-+LGRog6RAsCJrrrg/IO6LGmpphNe5DiK30dGjCoxxeGv49B10/3XYGxPsAwrDlMFcFEvdAUavDT8r9k/hSyQqQ==}
engines: {node: '>=6.9.0'}
'@babel/core@7.25.2':
resolution: {integrity: sha512-BBt3opiCOxUr9euZ5/ro/Xv8/V7yJ5bjYMqG/C1YAo8MIKAnumZalCN+msbci3Pigy4lIQfPUpfMM27HMGaYEA==}
engines: {node: '>=6.9.0'}
'@babel/generator@7.25.6':
resolution: {integrity: sha512-VPC82gr1seXOpkjAAKoLhP50vx4vGNlF4msF64dSFq1P8RfB+QAuJWGHPXXPc8QyfVWwwB/TNNU4+ayZmHNbZw==}
engines: {node: '>=6.9.0'}
'@babel/helper-annotate-as-pure@7.24.7':
resolution: {integrity: sha512-BaDeOonYvhdKw+JoMVkAixAAJzG2jVPIwWoKBPdYuY9b452e2rPuI9QPYh3KpofZ3pW2akOmwZLOiOsHMiqRAg==}
engines: {node: '>=6.9.0'}
'@babel/helper-compilation-targets@7.25.2':
resolution: {integrity: sha512-U2U5LsSaZ7TAt3cfaymQ8WHh0pxvdHoEk6HVpaexxixjyEquMh0L0YNJNM6CTGKMXV1iksi0iZkGw4AcFkPaaw==}
engines: {node: '>=6.9.0'}
'@babel/helper-create-class-features-plugin@7.24.7':
resolution: {integrity: sha512-kTkaDl7c9vO80zeX1rJxnuRpEsD5tA81yh11X1gQo+PhSti3JS+7qeZo9U4RHobKRiFPKaGK3svUAeb8D0Q7eg==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0
'@babel/helper-environment-visitor@7.24.7':
resolution: {integrity: sha512-DoiN84+4Gnd0ncbBOM9AZENV4a5ZiL39HYMyZJGZ/AZEykHYdJw0wW3kdcsh9/Kn+BRXHLkkklZ51ecPKmI1CQ==}
engines: {node: '>=6.9.0'}
'@babel/helper-function-name@7.24.7':
resolution: {integrity: sha512-FyoJTsj/PEUWu1/TYRiXTIHc8lbw+TDYkZuoE43opPS5TrI7MyONBE1oNvfguEXAD9yhQRrVBnXdXzSLQl9XnA==}
engines: {node: '>=6.9.0'}
'@babel/helper-member-expression-to-functions@7.24.7':
resolution: {integrity: sha512-LGeMaf5JN4hAT471eJdBs/GK1DoYIJ5GCtZN/EsL6KUiiDZOvO/eKE11AMZJa2zP4zk4qe9V2O/hxAmkRc8p6w==}
engines: {node: '>=6.9.0'}
'@babel/helper-module-imports@7.22.15':
resolution: {integrity: sha512-0pYVBnDKZO2fnSPCrgM/6WMc7eS20Fbok+0r88fp+YtWVLZrp4CkafFGIp+W0VKw4a22sgebPT99y+FDNMdP4w==}
engines: {node: '>=6.9.0'}
'@babel/helper-module-imports@7.24.7':
resolution: {integrity: sha512-8AyH3C+74cgCVVXow/myrynrAGv+nTVg5vKu2nZph9x7RcRwzmh0VFallJuFTZ9mx6u4eSdXZfcOzSqTUm0HCA==}
engines: {node: '>=6.9.0'}
'@babel/helper-module-transforms@7.25.2':
resolution: {integrity: sha512-BjyRAbix6j/wv83ftcVJmBt72QtHI56C7JXZoG2xATiLpmoC7dpd8WnkikExHDVPpi/3qCmO6WY1EaXOluiecQ==}
engines: {node: '>=6.9.0'}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0
'@babel/helper-optimise-call-expression@7.24.7':
resolution: {integrity: sha512-jKiTsW2xmWwxT1ixIdfXUZp+P5yURx2suzLZr5Hi64rURpDYdMW0pv+Uf17EYk2Rd428Lx4tLsnjGJzYKDM/6A==}
engines: {node: '>=6.9.0'}
'@babel/helper-plugin-utils@7.24.7':
resolution: {integrity: sha512-Rq76wjt7yz9AAc1KnlRKNAi/dMSVWgDRx43FHoJEbcYU6xOWaE2dVPwcdTukJrjxS65GITyfbvEYHvkirZ6uEg==}
engines: {node: '>=6.9.0'}
'@babel/helper-replace-supers@7.24.7':
resolution: {integrity: sha512-qTAxxBM81VEyoAY0TtLrx1oAEJc09ZK67Q9ljQToqCnA+55eNwCORaxlKyu+rNfX86o8OXRUSNUnrtsAZXM9sg==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0
'@babel/helper-simple-access@7.24.7':
resolution: {integrity: sha512-zBAIvbCMh5Ts+b86r/CjU+4XGYIs+R1j951gxI3KmmxBMhCg4oQMsv6ZXQ64XOm/cvzfU1FmoCyt6+owc5QMYg==}
engines: {node: '>=6.9.0'}
'@babel/helper-skip-transparent-expression-wrappers@7.24.7':
resolution: {integrity: sha512-IO+DLT3LQUElMbpzlatRASEyQtfhSE0+m465v++3jyyXeBTBUjtVZg28/gHeV5mrTJqvEKhKroBGAvhW+qPHiQ==}
engines: {node: '>=6.9.0'}
'@babel/helper-split-export-declaration@7.24.7':
resolution: {integrity: sha512-oy5V7pD+UvfkEATUKvIjvIAH/xCzfsFVw7ygW2SI6NClZzquT+mwdTfgfdbUiceh6iQO0CHtCPsyze/MZ2YbAA==}
engines: {node: '>=6.9.0'}
'@babel/helper-string-parser@7.24.8':
resolution: {integrity: sha512-pO9KhhRcuUyGnJWwyEgnRJTSIZHiT+vMD0kPeD+so0l7mxkMT19g3pjY9GTnHySck/hDzq+dtW/4VgnMkippsQ==}
engines: {node: '>=6.9.0'}
'@babel/helper-validator-identifier@7.24.7':
resolution: {integrity: sha512-rR+PBcQ1SMQDDyF6X0wxtG8QyLCgUB0eRAGguqRLfkCA87l7yAP7ehq8SNj96OOGTO8OBV70KhuFYcIkHXOg0w==}
engines: {node: '>=6.9.0'}
'@babel/helper-validator-option@7.24.8':
resolution: {integrity: sha512-xb8t9tD1MHLungh/AIoWYN+gVHaB9kwlu8gffXGSt3FFEIT7RjS+xWbc2vUD1UTZdIpKj/ab3rdqJ7ufngyi2Q==}
engines: {node: '>=6.9.0'}
'@babel/helpers@7.25.6':
resolution: {integrity: sha512-Xg0tn4HcfTijTwfDwYlvVCl43V6h4KyVVX2aEm4qdO/PC6L2YvzLHFdmxhoeSA3eslcE6+ZVXHgWwopXYLNq4Q==}
engines: {node: '>=6.9.0'}
'@babel/highlight@7.24.7':
resolution: {integrity: sha512-EStJpq4OuY8xYfhGVXngigBJRWxftKX9ksiGDnmlY3o7B/V7KIAc9X4oiK87uPJSc/vs5L869bem5fhZa8caZw==}
engines: {node: '>=6.9.0'}
'@babel/parser@7.25.6':
resolution: {integrity: sha512-trGdfBdbD0l1ZPmcJ83eNxB9rbEax4ALFTF7fN386TMYbeCQbyme5cOEXQhbGXKebwGaB/J52w1mrklMcbgy6Q==}
engines: {node: '>=6.0.0'}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
hasBin: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-proposal-decorators@7.24.7':
resolution: {integrity: sha512-RL9GR0pUG5Kc8BUWLNDm2T5OpYwSX15r98I0IkgmRQTXuELq/OynH8xtMTMvTJFjXbMWFVTKtYkTaYQsuAwQlQ==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/plugin-proposal-private-methods@7.18.6':
resolution: {integrity: sha512-nutsvktDItsNn4rpGItSNV2sz1XwS+nfU0Rg8aCx3W3NOKVzdMjJRu0O5OkgDp3ZGICSTbgRpxZoWsxoKRvbeA==}
engines: {node: '>=6.9.0'}
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
deprecated: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/plugin-syntax-decorators@7.24.7':
resolution: {integrity: sha512-Ui4uLJJrRV1lb38zg1yYTmRKmiZLiftDEvZN2iq3kd9kUFU+PttmzTbAFC2ucRk/XJmtek6G23gPsuZbhrT8fQ==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/plugin-syntax-import-attributes@7.24.7':
resolution: {integrity: sha512-hbX+lKKeUMGihnK8nvKqmXBInriT3GVjzXKFriV3YC6APGxMbP8RZNFwy91+hocLXq90Mta+HshoB31802bb8A==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-syntax-import-meta@7.10.4':
resolution: {integrity: sha512-Yqfm+XDx0+Prh3VSeEQCPU81yC+JWZ2pDPFSS4ZdpfZhp4MkFMaDC1UqseovEKwSUpnIL7+vK+Clp7bfh0iD7g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/plugin-syntax-jsx@7.24.7':
resolution: {integrity: sha512-6ddciUPe/mpMnOKv/U+RSd2vvVy+Yw/JfBB0ZHYjEZt9NLHmCUylNYlsbqCCS1Bffjlb0fCwC9Vqz+sBz6PsiQ==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/plugin-syntax-typescript@7.24.7':
resolution: {integrity: sha512-c/+fVeJBB0FeKsFvwytYiUD+LBvhHjGSI0g446PRGdSVGZLRNArBUno2PETbAly3tpiNAQR5XaZ+JslxkotsbA==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/plugin-transform-react-jsx-self@7.24.7':
resolution: {integrity: sha512-fOPQYbGSgH0HUp4UJO4sMBFjY6DuWq+2i8rixyUMb3CdGixs/gccURvYOAhajBdKDoGajFr3mUq5rH3phtkGzw==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/plugin-transform-react-jsx-source@7.24.7':
resolution: {integrity: sha512-J2z+MWzZHVOemyLweMqngXrgGC42jQ//R0KdxqkIz/OrbVIIlhFI3WigZ5fO+nwFvBlncr4MGapd8vTyc7RPNQ==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/plugin-transform-typescript@7.24.7':
resolution: {integrity: sha512-iLD3UNkgx2n/HrjBesVbYX6j0yqn/sJktvbtKKgcaLIQ4bTTQ8obAypc1VpyHPD2y4Phh9zHOaAt8e/L14wCpw==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@babel/runtime@7.24.7':
resolution: {integrity: sha512-UwgBRMjJP+xv857DCngvqXI3Iq6J4v0wXmwc6sapg+zyhbwmQX67LUEFrkK5tbyJ30jGuG3ZvWpBiB9LCy1kWw==}
engines: {node: '>=6.9.0'}
'@babel/template@7.25.0':
resolution: {integrity: sha512-aOOgh1/5XzKvg1jvVz7AVrx2piJ2XBi227DHmbY6y+bM9H2FlN+IfecYu4Xl0cNiiVejlsCri89LUsbj8vJD9Q==}
engines: {node: '>=6.9.0'}
'@babel/traverse@7.25.6':
resolution: {integrity: sha512-9Vrcx5ZW6UwK5tvqsj0nGpp/XzqthkT0dqIc9g1AdtygFToNtTF67XzYS//dm+SAK9cp3B9R4ZO/46p63SCjlQ==}
engines: {node: '>=6.9.0'}
'@babel/types@7.25.6':
resolution: {integrity: sha512-/l42B1qxpG6RdfYf343Uw1vmDjeNhneUXtzhojE7pDgfpEypmRhI6j1kr17XCVv4Cgl9HdAiQY2x0GwKm7rWCw==}
engines: {node: '>=6.9.0'}
'@bcoe/v8-coverage@0.2.3':
resolution: {integrity: sha512-0hYQ8SB4Db5zvZB4axdMHGwEaQjkZzFjQiN9LVYvIFB2nSUHW9tYpxWriPrWDASIxiaXax83REcLxuSdnGPZtw==}
'@codemirror/autocomplete@6.16.3':
resolution: {integrity: sha512-Vl/tIeRVVUCRDuOG48lttBasNQu8usGgXQawBXI7WJAiUDSFOfzflmEsZFZo48mAvAaa4FZ/4/yLLxFtdJaKYA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/language': ^6.0.0
'@codemirror/state': ^6.0.0
'@codemirror/view': ^6.0.0
'@lezer/common': ^1.0.0
'@codemirror/commands@6.6.0':
resolution: {integrity: sha512-qnY+b7j1UNcTS31Eenuc/5YJB6gQOzkUoNmJQc0rznwqSRpeaWWpjkWy2C/MPTcePpsKJEM26hXrOXl1+nceXg==}
'@codemirror/lang-css@6.3.0':
resolution: {integrity: sha512-CyR4rUNG9OYcXDZwMPvJdtb6PHbBDKUc/6Na2BIwZ6dKab1JQqKa4di+RNRY9Myn7JB81vayKwJeQ7jEdmNVDA==}
'@codemirror/lang-html@6.4.9':
resolution: {integrity: sha512-aQv37pIMSlueybId/2PVSP6NPnmurFDVmZwzc7jszd2KAF8qd4VBbvNYPXWQq90WIARjsdVkPbw29pszmHws3Q==}
'@codemirror/lang-javascript@6.2.2':
resolution: {integrity: sha512-VGQfY+FCc285AhWuwjYxQyUQcYurWlxdKYT4bqwr3Twnd5wP5WSeu52t4tvvuWmljT4EmgEgZCqSieokhtY8hg==}
'@codemirror/lang-json@6.0.1':
resolution: {integrity: sha512-+T1flHdgpqDDlJZ2Lkil/rLiRy684WMLc74xUnjJH48GQdfJo/pudlTRreZmKwzP8/tGdKf83wlbAdOCzlJOGQ==}
'@codemirror/lang-markdown@6.3.0':
resolution: {integrity: sha512-lYrI8SdL/vhd0w0aHIEvIRLRecLF7MiiRfzXFZY94dFwHqC9HtgxgagJ8fyYNBldijGatf9wkms60d8SrAj6Nw==}
'@codemirror/language@6.10.2':
resolution: {integrity: sha512-kgbTYTo0Au6dCSc/TFy7fK3fpJmgHDv1sG1KNQKJXVi+xBTEeBPY/M30YXiU6mMXeH+YIDLsbrT4ZwNRdtF+SA==}
'@codemirror/lint@6.8.1':
resolution: {integrity: sha512-IZ0Y7S4/bpaunwggW2jYqwLuHj0QtESf5xcROewY6+lDNwZ/NzvR4t+vpYgg9m7V8UXLPYqG+lu3DF470E5Oxg==}
'@codemirror/search@6.5.6':
resolution: {integrity: sha512-rpMgcsh7o0GuCDUXKPvww+muLA1pDJaFrpq/CCHtpQJYz8xopu4D1hPcKRoDD0YlF8gZaqTNIRa4VRBWyhyy7Q==}
'@codemirror/state@6.4.1':
resolution: {integrity: sha512-QkEyUiLhsJoZkbumGZlswmAhA7CBU02Wrz7zvH4SrcifbsqwlXShVXg65f3v/ts57W3dqyamEriMhij1Z3Zz4A==}
'@codemirror/theme-one-dark@6.1.2':
resolution: {integrity: sha512-F+sH0X16j/qFLMAfbciKTxVOwkdAS336b7AXTKOZhy8BR3eH/RelsnLgLFINrpST63mmN2OuwUt0W2ndUgYwUA==}
'@codemirror/view@6.28.3':
resolution: {integrity: sha512-QVqP+ko078/h9yrW+u5grX3rQhC+BkGKADRrlDaJznfPngJOv5zObiVf0+SgAWhL/Yt0nvZ+10rO3L+gU5IbFw==}
'@csstools/selector-resolve-nested@1.1.0':
resolution: {integrity: sha512-uWvSaeRcHyeNenKg8tp17EVDRkpflmdyvbE0DHo6D/GdBb6PDnCYYU6gRpXhtICMGMcahQmj2zGxwFM/WC8hCg==}
engines: {node: ^14 || ^16 || >=18}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
postcss-selector-parser: ^6.0.13
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@csstools/selector-specificity@3.1.1':
resolution: {integrity: sha512-a7cxGcJ2wIlMFLlh8z2ONm+715QkPHiyJcxwQlKOz/03GPw1COpfhcmC9wm4xlZfp//jWHNNMwzjtqHXVWU9KA==}
engines: {node: ^14 || ^16 || >=18}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
postcss-selector-parser: ^6.0.13
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@danmarshall/deckgl-typings@4.9.28':
resolution: {integrity: sha512-cvp0sPunaOgzI/6Kb9zQjNPOegFrli8t/mWLESTDarZT1xBGe9FwLQ9wQT0XFcVagdlhe2NFBx0oeRy0L4f1GQ==}
'@develar/schema-utils@2.6.5':
resolution: {integrity: sha512-0cp4PsWQ/9avqTVMCtZ+GirikIA36ikvjtHweU4/j8yLtgObI0+JUPhYFScgwlteveGB1rt3Cm8UhN04XayDig==}
engines: {node: '>= 8.9.0'}
'@electron/asar@3.2.10':
resolution: {integrity: sha512-mvBSwIBUeiRscrCeJE1LwctAriBj65eUDm0Pc11iE5gRwzkmsdbS7FnZ1XUWjpSeQWL1L5g12Fc/SchPM9DUOw==}
engines: {node: '>=10.12.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/get@2.0.3':
resolution: {integrity: sha512-Qkzpg2s9GnVV2I2BjRksUi43U5e6+zaQMcjoJy0C+C5oxaKl+fmckGDQFtRpZpZV0NQekuZZ+tGz7EA9TVnQtQ==}
engines: {node: '>=12'}
'@electron/notarize@2.1.0':
resolution: {integrity: sha512-Q02xem1D0sg4v437xHgmBLxI2iz/fc0D4K7fiVWHa/AnW8o7D751xyKNXgziA6HrTOme9ul1JfWN5ark8WH1xA==}
engines: {node: '>= 10.0.0'}
'@electron/notarize@2.2.1':
resolution: {integrity: sha512-aL+bFMIkpR0cmmj5Zgy0LMKEpgy43/hw5zadEArgmAMWWlKc5buwFvFT9G/o/YJkvXAJm5q3iuTuLaiaXW39sg==}
engines: {node: '>= 10.0.0'}
'@electron/osx-sign@1.0.5':
resolution: {integrity: sha512-k9ZzUQtamSoweGQDV2jILiRIHUu7lYlJ3c6IEmjv1hC17rclE+eb9U+f6UFlOOETo0JzY1HNlXy4YOlCvl+Lww==}
engines: {node: '>=12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/universal@1.5.1':
resolution: {integrity: sha512-kbgXxyEauPJiQQUNG2VgUeyfQNFk6hBF11ISN2PNI6agUgPl55pv4eQmaqHzTAzchBvqZ2tQuRVaPStGf0mxGw==}
engines: {node: '>=8.6'}
'@emotion/is-prop-valid@1.3.0':
resolution: {integrity: sha512-SHetuSLvJDzuNbOdtPVbq6yMMMlLoW5Q94uDqJZqy50gcmAjxFkVqmzqSGEFq9gT2iMuIeKV1PXVWmvUhuZLlQ==}
'@emotion/memoize@0.9.0':
resolution: {integrity: sha512-30FAj7/EoJ5mwVPOWhAyCX+FPfMDrVecJAM+Iw9NRoSl4BBAQeqj4cApHHUXOVvIPgLVDsCFoz/hGD+5QQD1GQ==}
'@es-joy/jsdoccomment@0.49.0':
resolution: {integrity: sha512-xjZTSFgECpb9Ohuk5yMX5RhUEbfeQcuOp8IF60e+wyzWEF0M5xeSgqsfLtvPEX8BIyOX9saZqzuGPmZ8oWc+5Q==}
engines: {node: '>=16'}
'@esbuild/aix-ppc64@0.21.5':
resolution: {integrity: sha512-1SDgH6ZSPTlggy1yI6+Dbkiz8xzpHJEVAlF/AM1tHPLsf5STom9rwtjE4hKAF20FfXXNTFqEYXyJNWh1GiZedQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [ppc64]
os: [aix]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/aix-ppc64@0.23.0':
resolution: {integrity: sha512-3sG8Zwa5fMcA9bgqB8AfWPQ+HFke6uD3h1s3RIwUNK8EG7a4buxvuFTs3j1IMs2NXAk9F30C/FF4vxRgQCcmoQ==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [ppc64]
os: [aix]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-arm64@0.21.5':
resolution: {integrity: sha512-c0uX9VAUBQ7dTDCjq+wdyGLowMdtR/GoC2U5IYk/7D1H1JYC0qseD7+11iMP2mRLN9RcCMRcjC4YMclCzGwS/A==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm64]
os: [android]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-arm64@0.23.0':
resolution: {integrity: sha512-EuHFUYkAVfU4qBdyivULuu03FhJO4IJN9PGuABGrFy4vUuzk91P2d+npxHcFdpUnfYKy0PuV+n6bKIpHOB3prQ==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [arm64]
os: [android]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-arm@0.21.5':
resolution: {integrity: sha512-vCPvzSjpPHEi1siZdlvAlsPxXl7WbOVUBBAowWug4rJHb68Ox8KualB+1ocNvT5fjv6wpkX6o/iEpbDrf68zcg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm]
os: [android]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-arm@0.23.0':
resolution: {integrity: sha512-+KuOHTKKyIKgEEqKbGTK8W7mPp+hKinbMBeEnNzjJGyFcWsfrXjSTNluJHCY1RqhxFurdD8uNXQDei7qDlR6+g==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [arm]
os: [android]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-x64@0.21.5':
resolution: {integrity: sha512-D7aPRUUNHRBwHxzxRvp856rjUHRFW1SdQATKXH2hqA0kAZb1hKmi02OpYRacl0TxIGz/ZmXWlbZgjwWYaCakTA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [android]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-x64@0.23.0':
resolution: {integrity: sha512-WRrmKidLoKDl56LsbBMhzTTBxrsVwTKdNbKDalbEZr0tcsBgCLbEtoNthOW6PX942YiYq8HzEnb4yWQMLQuipQ==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [x64]
os: [android]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/darwin-arm64@0.21.5':
resolution: {integrity: sha512-DwqXqZyuk5AiWWf3UfLiRDJ5EDd49zg6O9wclZ7kUMv2WRFr4HKjXp/5t8JZ11QbQfUS6/cRCKGwYhtNAY88kQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm64]
os: [darwin]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/darwin-arm64@0.23.0':
resolution: {integrity: sha512-YLntie/IdS31H54Ogdn+v50NuoWF5BDkEUFpiOChVa9UnKpftgwzZRrI4J132ETIi+D8n6xh9IviFV3eXdxfow==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [arm64]
os: [darwin]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/darwin-x64@0.21.5':
resolution: {integrity: sha512-se/JjF8NlmKVG4kNIuyWMV/22ZaerB+qaSi5MdrXtd6R08kvs2qCN4C09miupktDitvh8jRFflwGFBQcxZRjbw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [darwin]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/darwin-x64@0.23.0':
resolution: {integrity: sha512-IMQ6eme4AfznElesHUPDZ+teuGwoRmVuuixu7sv92ZkdQcPbsNHzutd+rAfaBKo8YK3IrBEi9SLLKWJdEvJniQ==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [x64]
os: [darwin]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/freebsd-arm64@0.21.5':
resolution: {integrity: sha512-5JcRxxRDUJLX8JXp/wcBCy3pENnCgBR9bN6JsY4OmhfUtIHe3ZW0mawA7+RDAcMLrMIZaf03NlQiX9DGyB8h4g==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm64]
os: [freebsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/freebsd-arm64@0.23.0':
resolution: {integrity: sha512-0muYWCng5vqaxobq6LB3YNtevDFSAZGlgtLoAc81PjUfiFz36n4KMpwhtAd4he8ToSI3TGyuhyx5xmiWNYZFyw==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [arm64]
os: [freebsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/freebsd-x64@0.21.5':
resolution: {integrity: sha512-J95kNBj1zkbMXtHVH29bBriQygMXqoVQOQYA+ISs0/2l3T9/kj42ow2mpqerRBxDJnmkUDCaQT/dfNXWX/ZZCQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [freebsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/freebsd-x64@0.23.0':
resolution: {integrity: sha512-XKDVu8IsD0/q3foBzsXGt/KjD/yTKBCIwOHE1XwiXmrRwrX6Hbnd5Eqn/WvDekddK21tfszBSrE/WMaZh+1buQ==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [x64]
os: [freebsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-arm64@0.21.5':
resolution: {integrity: sha512-ibKvmyYzKsBeX8d8I7MH/TMfWDXBF3db4qM6sy+7re0YXya+K1cem3on9XgdT2EQGMu4hQyZhan7TeQ8XkGp4Q==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-arm64@0.23.0':
resolution: {integrity: sha512-j1t5iG8jE7BhonbsEg5d9qOYcVZv/Rv6tghaXM/Ug9xahM0nX/H2gfu6X6z11QRTMT6+aywOMA8TDkhPo8aCGw==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [arm64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-arm@0.21.5':
resolution: {integrity: sha512-bPb5AHZtbeNGjCKVZ9UGqGwo8EUu4cLq68E95A53KlxAPRmUyYv2D6F0uUI65XisGOL1hBP5mTronbgo+0bFcA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-arm@0.23.0':
resolution: {integrity: sha512-SEELSTEtOFu5LPykzA395Mc+54RMg1EUgXP+iw2SJ72+ooMwVsgfuwXo5Fn0wXNgWZsTVHwY2cg4Vi/bOD88qw==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [arm]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-ia32@0.21.5':
resolution: {integrity: sha512-YvjXDqLRqPDl2dvRODYmmhz4rPeVKYvppfGYKSNGdyZkA01046pLWyRKKI3ax8fbJoK5QbxblURkwK/MWY18Tg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [ia32]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-ia32@0.23.0':
resolution: {integrity: sha512-P7O5Tkh2NbgIm2R6x1zGJJsnacDzTFcRWZyTTMgFdVit6E98LTxO+v8LCCLWRvPrjdzXHx9FEOA8oAZPyApWUA==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [ia32]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-loong64@0.21.5':
resolution: {integrity: sha512-uHf1BmMG8qEvzdrzAqg2SIG/02+4/DHB6a9Kbya0XDvwDEKCoC8ZRWI5JJvNdUjtciBGFQ5PuBlpEOXQj+JQSg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [loong64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-loong64@0.23.0':
resolution: {integrity: sha512-InQwepswq6urikQiIC/kkx412fqUZudBO4SYKu0N+tGhXRWUqAx+Q+341tFV6QdBifpjYgUndV1hhMq3WeJi7A==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [loong64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-mips64el@0.21.5':
resolution: {integrity: sha512-IajOmO+KJK23bj52dFSNCMsz1QP1DqM6cwLUv3W1QwyxkyIWecfafnI555fvSGqEKwjMXVLokcV5ygHW5b3Jbg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [mips64el]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-mips64el@0.23.0':
resolution: {integrity: sha512-J9rflLtqdYrxHv2FqXE2i1ELgNjT+JFURt/uDMoPQLcjWQA5wDKgQA4t/dTqGa88ZVECKaD0TctwsUfHbVoi4w==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [mips64el]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-ppc64@0.21.5':
resolution: {integrity: sha512-1hHV/Z4OEfMwpLO8rp7CvlhBDnjsC3CttJXIhBi+5Aj5r+MBvy4egg7wCbe//hSsT+RvDAG7s81tAvpL2XAE4w==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [ppc64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-ppc64@0.23.0':
resolution: {integrity: sha512-cShCXtEOVc5GxU0fM+dsFD10qZ5UpcQ8AM22bYj0u/yaAykWnqXJDpd77ublcX6vdDsWLuweeuSNZk4yUxZwtw==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [ppc64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-riscv64@0.21.5':
resolution: {integrity: sha512-2HdXDMd9GMgTGrPWnJzP2ALSokE/0O5HhTUvWIbD3YdjME8JwvSCnNGBnTThKGEB91OZhzrJ4qIIxk/SBmyDDA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [riscv64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-riscv64@0.23.0':
resolution: {integrity: sha512-HEtaN7Y5UB4tZPeQmgz/UhzoEyYftbMXrBCUjINGjh3uil+rB/QzzpMshz3cNUxqXN7Vr93zzVtpIDL99t9aRw==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [riscv64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-s390x@0.21.5':
resolution: {integrity: sha512-zus5sxzqBJD3eXxwvjN1yQkRepANgxE9lgOW2qLnmr8ikMTphkjgXu1HR01K4FJg8h1kEEDAqDcZQtbrRnB41A==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [s390x]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-s390x@0.23.0':
resolution: {integrity: sha512-WDi3+NVAuyjg/Wxi+o5KPqRbZY0QhI9TjrEEm+8dmpY9Xir8+HE/HNx2JoLckhKbFopW0RdO2D72w8trZOV+Wg==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [s390x]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-x64@0.21.5':
resolution: {integrity: sha512-1rYdTpyv03iycF1+BhzrzQJCdOuAOtaqHTWJZCWvijKD2N5Xu0TtVC8/+1faWqcP9iBCWOmjmhoH94dH82BxPQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-x64@0.23.0':
resolution: {integrity: sha512-a3pMQhUEJkITgAw6e0bWA+F+vFtCciMjW/LPtoj99MhVt+Mfb6bbL9hu2wmTZgNd994qTAEw+U/r6k3qHWWaOQ==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [x64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/netbsd-x64@0.21.5':
resolution: {integrity: sha512-Woi2MXzXjMULccIwMnLciyZH4nCIMpWQAs049KEeMvOcNADVxo0UBIQPfSmxB3CWKedngg7sWZdLvLczpe0tLg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [netbsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/netbsd-x64@0.23.0':
resolution: {integrity: sha512-cRK+YDem7lFTs2Q5nEv/HHc4LnrfBCbH5+JHu6wm2eP+d8OZNoSMYgPZJq78vqQ9g+9+nMuIsAO7skzphRXHyw==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [x64]
os: [netbsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/openbsd-arm64@0.23.0':
resolution: {integrity: sha512-suXjq53gERueVWu0OKxzWqk7NxiUWSUlrxoZK7usiF50C6ipColGR5qie2496iKGYNLhDZkPxBI3erbnYkU0rQ==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [arm64]
os: [openbsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/openbsd-x64@0.21.5':
resolution: {integrity: sha512-HLNNw99xsvx12lFBUwoT8EVCsSvRNDVxNpjZ7bPn947b8gJPzeHWyNVhFsaerc0n3TsbOINvRP2byTZ5LKezow==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [openbsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/openbsd-x64@0.23.0':
resolution: {integrity: sha512-6p3nHpby0DM/v15IFKMjAaayFhqnXV52aEmv1whZHX56pdkK+MEaLoQWj+H42ssFarP1PcomVhbsR4pkz09qBg==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [x64]
os: [openbsd]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/sunos-x64@0.21.5':
resolution: {integrity: sha512-6+gjmFpfy0BHU5Tpptkuh8+uw3mnrvgs+dSPQXQOv3ekbordwnzTVEb4qnIvQcYXq6gzkyTnoZ9dZG+D4garKg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [sunos]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/sunos-x64@0.23.0':
resolution: {integrity: sha512-BFelBGfrBwk6LVrmFzCq1u1dZbG4zy/Kp93w2+y83Q5UGYF1d8sCzeLI9NXjKyujjBBniQa8R8PzLFAUrSM9OA==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [x64]
os: [sunos]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-arm64@0.21.5':
resolution: {integrity: sha512-Z0gOTd75VvXqyq7nsl93zwahcTROgqvuAcYDUr+vOv8uHhNSKROyU961kgtCD1e95IqPKSQKH7tBTslnS3tA8A==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm64]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-arm64@0.23.0':
resolution: {integrity: sha512-lY6AC8p4Cnb7xYHuIxQ6iYPe6MfO2CC43XXKo9nBXDb35krYt7KGhQnOkRGar5psxYkircpCqfbNDB4uJbS2jQ==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [arm64]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-ia32@0.21.5':
resolution: {integrity: sha512-SWXFF1CL2RVNMaVs+BBClwtfZSvDgtL//G/smwAc5oVK/UPu2Gu9tIaRgFmYFFKrmg3SyAjSrElf0TiJ1v8fYA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [ia32]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-ia32@0.23.0':
resolution: {integrity: sha512-7L1bHlOTcO4ByvI7OXVI5pNN6HSu6pUQq9yodga8izeuB1KcT2UkHaH6118QJwopExPn0rMHIseCTx1CRo/uNA==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [ia32]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-x64@0.21.5':
resolution: {integrity: sha512-tQd/1efJuzPC6rCFwEvLtci/xNFcTZknmXs98FYDfGE4wP9ClFV98nyKrzJKVPMhdDnjzLhdUyMX4PsQAPjwIw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-x64@0.23.0':
resolution: {integrity: sha512-Arm+WgUFLUATuoxCJcahGuk6Yj9Pzxd6l11Zb/2aAuv5kWWvvfhLFo2fni4uSK5vzlUdCGZ/BdV5tH8klj8p8g==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
cpu: [x64]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint-community/eslint-utils@4.4.0':
resolution: {integrity: sha512-1/sA4dwrzBAyeUoQ6oxahHKmrZvsnLCg4RfxW3ZFGGmQkSNQPFNLV9CUEFQP1x9EYXHTo5p6xdhZM1Ne9p/AfA==}
engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
eslint: ^6.0.0 || ^7.0.0 || >=8.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint-community/regexpp@4.11.0':
resolution: {integrity: sha512-G/M/tIiMrTAxEWRfLfQJMmGNX28IxBg4PBz8XqQhqUHLFI6TL2htpIB1iQCj144V5ee/JaKyT9/WZ0MGZWfA7A==}
engines: {node: ^12.0.0 || ^14.0.0 || >=16.0.0}
'@eslint/config-array@0.18.0':
resolution: {integrity: sha512-fTxvnS1sRMu3+JjXwJG0j/i4RT9u4qJ+lqS/yCGap4lH4zZGzQ7tu+xZqQmcMZq5OBZDL4QRxQzRjkWcGt8IVw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@eslint/core@0.7.0':
resolution: {integrity: sha512-xp5Jirz5DyPYlPiKat8jaq0EmYvDXKKpzTbxXMpT9eqlRJkRKIz9AGMdlvYjih+im+QlhWrpvVjl8IPC/lHlUw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@eslint/eslintrc@3.1.0':
resolution: {integrity: sha512-4Bfj15dVJdoy3RfZmmo86RK1Fwzn6SstsvK9JS+BaVKqC6QQQQyXekNaC+g+LKNgkQ+2VhGAzm6hO40AhMR3zQ==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@eslint/js@9.13.0':
resolution: {integrity: sha512-IFLyoY4d72Z5y/6o/BazFBezupzI/taV8sGumxTAVw3lXG9A6md1Dc34T9s1FoD/an9pJH8RHbAxsaEbBed9lA==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@eslint/object-schema@2.1.4':
resolution: {integrity: sha512-BsWiH1yFGjXXS2yvrf5LyuoSIIbPrGUWob917o+BTKuZ7qJdxX8aJLRxs1fS9n6r7vESrq1OUqb68dANcFXuQQ==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@eslint/plugin-kit@0.2.1':
resolution: {integrity: sha512-HFZ4Mp26nbWk9d/BpvP0YNL6W4UoZF0VFcTw/aPPA8RpOxeFQgK+ClABGgAUXs9Y/RGX/l1vOmrqz1MQt9MNuw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@fal-works/esbuild-plugin-global-externals@2.1.2':
resolution: {integrity: sha512-cEee/Z+I12mZcFJshKcCqC8tuX5hG3s+d+9nZ3LabqKF1vKdF41B92pJVCBggjAGORAeOzyyDDKrZwIkLffeOQ==}
'@fast-check/vitest@0.0.8':
resolution: {integrity: sha512-cFrcu7nwH+rk1qm1J4YrM1k4MIwvIHG7MrQUMGizqPe58XsvvpZz0X9Xkx1e+xaNg9s1YRVTd241WSR0dK/SpQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
vitest: '>=0.28.1'
'@floating-ui/core@1.6.4':
resolution: {integrity: sha512-a4IowK4QkXl4SCWTGUR0INAfEOX3wtsYw3rKK5InQEHMGObkR8Xk44qYQD9P4r6HHw0iIfK6GUKECmY8sTkqRA==}
'@floating-ui/dom@1.1.1':
resolution: {integrity: sha512-TpIO93+DIujg3g7SykEAGZMDtbJRrmnYRCNYSjJlvIbGhBjRSNTLVbNeDQBrzy9qDgUbiWdc7KA0uZHZ2tJmiw==}
'@floating-ui/dom@1.6.7':
resolution: {integrity: sha512-wmVfPG5o2xnKDU4jx/m4w5qva9FWHcnZ8BvzEe90D/RpwsJaTAVYPEPdQ8sbr/N8zZTAHlZUTQdqg8ZUbzHmng==}
'@floating-ui/utils@0.2.4':
resolution: {integrity: sha512-dWO2pw8hhi+WrXq1YJy2yCuWoL20PddgGaqTgVe4cOS9Q6qklXCiA1tJEqX6BEwRNSCP84/afac9hd4MS+zEUA==}
'@floating-ui/vue@1.1.0':
resolution: {integrity: sha512-+Qq6K0zYcGZ6JoJXiL0z2gHh+77GyGhwXJMDiRx23tbYHLbQokw8DSC+cGIecjW8z7j3aWtSDtZyB1pNw2QBPA==}
'@formatjs/ecma402-abstract@2.0.0':
resolution: {integrity: sha512-rRqXOqdFmk7RYvj4khklyqzcfQl9vEL/usogncBHRZfZBDOwMGuSRNFl02fu5KGHXdbinju+YXyuR+Nk8xlr/g==}
'@formatjs/fast-memoize@2.2.0':
resolution: {integrity: sha512-hnk/nY8FyrL5YxwP9e4r9dqeM6cAbo8PeU9UjyXojZMNvVad2Z06FAVHyR3Ecw6fza+0GH7vdJgiKIVXTMbSBA==}
'@formatjs/icu-messageformat-parser@2.7.8':
resolution: {integrity: sha512-nBZJYmhpcSX0WeJ5SDYUkZ42AgR3xiyhNCsQweFx3cz/ULJjym8bHAzWKvG5e2+1XO98dBYC0fWeeAECAVSwLA==}
'@formatjs/icu-skeleton-parser@1.8.2':
resolution: {integrity: sha512-k4ERKgw7aKGWJZgTarIcNEmvyTVD9FYh0mTrrBMHZ1b8hUu6iOJ4SzsZlo3UNAvHYa+PnvntIwRPt1/vy4nA9Q==}
'@formatjs/intl-localematcher@0.5.4':
resolution: {integrity: sha512-zTwEpWOzZ2CiKcB93BLngUX59hQkuZjT2+SAQEscSm52peDW/getsawMcWF1rGRpMCX6D7nSJA3CzJ8gn13N/g==}
'@histoire/app@0.17.17':
resolution: {integrity: sha512-2i1V38o08V+eaR0d3L0/EA6AYG14xyQBJbyYv0Hz3r4sH3Elj1FoJiwolbCfTDmkOnSgwWTc7+JoCqkLIbxfhA==}
'@histoire/controls@0.17.17':
resolution: {integrity: sha512-W22HZ/X078IZmE09XEKj4Fq7LxQPP/w/aMYAzm94V2NIGhI0fkiSaBDvyTUl7NYrGT66Wq5+9Po1IWPMllk3cQ==}
'@histoire/plugin-vue@0.17.17':
resolution: {integrity: sha512-O5h/Ww6IT2CygVVT4onN27IZt11Z2qE8XeHeXJCEese3dxnnVWRhjMpsaWAU5XqgfjKNAiALJk86b49/6NQaRg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
histoire: ^0.17.17
vue: ^3.2.47
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/shared@0.17.17':
resolution: {integrity: sha512-ueGtURysonT0MujCObPCR57+mgZluMEXCrbc2FBgKAD/DoAt38tNwSGsmLldk2O6nTr7lr6ClbVSgWrLwgY6Xw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vite: ^2.9.0 || ^3.0.0 || ^4.0.0 || ^5.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/vendors@0.17.17':
resolution: {integrity: sha512-QZvmffdoJlLuYftPIkOU5Q2FPAdG2JjMuQ5jF7NmEl0n1XnmbMqtRkdYTZ4eF6CO1KLZ0Zyf6gBQvoT1uWNcjA==}
'@hookform/resolvers@3.6.0':
resolution: {integrity: sha512-UBcpyOX3+RR+dNnqBd0lchXpoL8p4xC21XP8H6Meb8uve5Br1GCnmg0PcBoKKqPKgGu9GHQ/oygcmPrQhetwqw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
react-hook-form: ^7.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@humanfs/core@0.19.0':
resolution: {integrity: sha512-2cbWIHbZVEweE853g8jymffCA+NCMiuqeECeBBLm8dg2oFdjuGJhgN4UAbI+6v0CKbbhvtXA4qV8YR5Ji86nmw==}
engines: {node: '>=18.18.0'}
'@humanfs/node@0.16.5':
resolution: {integrity: sha512-KSPA4umqSG4LHYRodq31VDwKAvaTF4xmVlzM8Aeh4PlU1JQ3IG0wiA8C25d3RQ9nJyM3mBHyI53K06VVL/oFFg==}
engines: {node: '>=18.18.0'}
'@humanwhocodes/module-importer@1.0.1':
resolution: {integrity: sha512-bxveV4V8v5Yb4ncFTT3rPSgZBOpCkjfK0y4oVVVJwIuDVBRMDXrPyXRL988i5ap9m9bnyEEjWfm5WkBmtffLfA==}
engines: {node: '>=12.22'}
'@humanwhocodes/retry@0.3.1':
resolution: {integrity: sha512-JBxkERygn7Bv/GbN5Rv8Ul6LVknS+5Bp6RgDC/O8gEBU/yeH5Ui5C/OlWrTb6qct7LjjfT6Re2NxB0ln0yYybA==}
engines: {node: '>=18.18'}
'@ianvs/prettier-plugin-sort-imports@4.3.0':
resolution: {integrity: sha512-OOMtUcO4J3LoL63dOKAe7bn+lSRRPeit2DqNHpx+wvBp3Grejo2PMaK4Mp1mwy8pnat64ccSgk/lBZbsAdLErw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-sfc': 2.7.x || 3.x
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prettier: 2 || 3
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-sfc':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date@3.5.5':
resolution: {integrity: sha512-H+CfYvOZ0LTJeeLOqm19E3uj/4YjrmOFtBufDHPfvtI80hFAMqtrp7oCACpe4Cil5l8S0Qu/9dYfZc/5lY8WQQ==}
'@internationalized/message@3.1.4':
resolution: {integrity: sha512-Dygi9hH1s7V9nha07pggCkvmRfDd3q2lWnMGvrJyrOwYMe1yj4D2T9BoH9I6MGR7xz0biQrtLPsqUkqXzIrBOw==}
'@internationalized/number@3.5.3':
resolution: {integrity: sha512-rd1wA3ebzlp0Mehj5YTuTI50AQEx80gWFyHcQu+u91/5NgdwBecO8BH6ipPfE+lmQ9d63vpB3H9SHoIUiupllw==}
'@internationalized/string@3.2.3':
resolution: {integrity: sha512-9kpfLoA8HegiWTeCbR2livhdVeKobCnVv8tlJ6M2jF+4tcMqDo94ezwlnrUANBWPgd8U7OXIHCk2Ov2qhk4KXw==}
'@isaacs/cliui@8.0.2':
resolution: {integrity: sha512-O8jcjabXaleOG9DQ0+ARXWZBTfnP4WNAqzuiJK7ll44AmxGKv/J2M4TPjxjY3znBCfvBXFzucm1twdyFybFqEA==}
engines: {node: '>=12'}
'@istanbuljs/schema@0.1.3':
resolution: {integrity: sha512-ZXRY4jNvVgSVQ8DL3LTcakaAtXwTVUxE81hslsyD2AtoXW/wVob10HkOJ1X/pAlcI7D+2YoZKg5do8G/w6RYgA==}
engines: {node: '>=8'}
'@jest/schemas@29.6.3':
resolution: {integrity: sha512-mo5j5X+jIZmJQveBKeS/clAueipV7KgiX1vMgCxam1RNYiqE1w62n0/tJJnHtjW8ZHcQco5gY85jA3mi0L+nSA==}
engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
'@jridgewell/gen-mapping@0.3.5':
resolution: {integrity: sha512-IzL8ZoEDIBRWEzlCcRhOaCupYyN5gdIK+Q6fbFdPDg6HqX6jpkItn7DFIpW9LQzXG6Df9sA7+OKnq0qlz/GaQg==}
engines: {node: '>=6.0.0'}
'@jridgewell/resolve-uri@3.1.2':
resolution: {integrity: sha512-bRISgCIjP20/tbWSPWMEi54QVPRZExkuD9lJL+UIxUKtwVJA8wW1Trb1jMs1RFXo1CBTNZ/5hpC9QvmKWdopKw==}
engines: {node: '>=6.0.0'}
'@jridgewell/set-array@1.2.1':
resolution: {integrity: sha512-R8gLRTZeyp03ymzP/6Lil/28tGeGEzhx1q2k703KGWRAI1VdvPIXdG70VJc2pAMw3NA6JKL5hhFu1sJX0Mnn/A==}
engines: {node: '>=6.0.0'}
'@jridgewell/sourcemap-codec@1.5.0':
resolution: {integrity: sha512-gv3ZRaISU3fjPAgNsriBRqGWQL6quFx04YMPW/zD8XMLsU32mhCCbfbO6KZFLjvYpCZ8zyDEgqsgf+PwPaM7GQ==}
'@jridgewell/trace-mapping@0.3.25':
resolution: {integrity: sha512-vNk6aEwybGtawWmy/PzwnGDOjCkLWSD2wqvjGGAgOAwCGWySYXfYoxt00IJkTF+8Lb57DwOb3Aa0o9CApepiYQ==}
'@json-schema-spec/json-pointer@0.1.2':
resolution: {integrity: sha512-BYY7IavBjwsWWSmVcMz2A9mKiDD9RvacnsItgmy1xV8cmgbtxFfKmKMtkVpD7pYtkx4mIW4800yZBXueVFIWPw==}
'@json-schema-tools/dereferencer@1.6.3':
resolution: {integrity: sha512-NoQkj6hx9Joqbd/GZAOHSGtE6R+OzlnOcDfyidmx8e/CUv1Q+Z6/fmZo2wwCQWiwP1pnGYc95iKwp8M7XlV7wQ==}
'@json-schema-tools/meta-schema@1.7.5':
resolution: {integrity: sha512-8Hy6tuMC2BQdK7O4ilLovFB9t0j5o0L/sQTuWeg2CNYpITmPiFTRiG7Yb/jYd483D8784kxLFJ0dT+T4O2hNmw==}
'@json-schema-tools/reference-resolver@1.2.6':
resolution: {integrity: sha512-4QZu5ROb5EpLSvV+buzk8WR30W+dffSNaKqD3VGFYJ3y0BLDi2OHoSz5e6NKcLYTyUYXV8IKxocNOszeVBJI4Q==}
'@json-schema-tools/traverse@1.10.4':
resolution: {integrity: sha512-9e42zjhLIxzBONroNC4SGsTqdB877tzwH2S6lqgTav9K24kWJR9vNieeMVSuyqnY8FlclH21D8wsm/tuD9WA9Q==}
'@lexical/clipboard@0.16.0':
resolution: {integrity: sha512-eYMJ6jCXpWBVC05Mu9HLMysrBbfi++xFfsm+Yo7A6kYGrqYUhpXqjJkYnw1xdZYL3bV73Oe4ByVJuq42GU+Mqw==}
'@lexical/html@0.16.0':
resolution: {integrity: sha512-okxn3q/1qkUpCZNEFRI39XeJj4YRjb6prm3WqZgP4d39DI1W24feeTZJjYRCW+dc3NInwFaolU3pNA2MGkjRtg==}
'@lexical/link@0.16.0':
resolution: {integrity: sha512-ppvJSh/XGqlzbeymOiwcXJcUcrqgQqTK2QXTBAZq7JThtb0WsJxYd2CSLSN+Ycu23prnwqOqILcU0+34+gAVFw==}
'@lexical/list@0.16.0':
resolution: {integrity: sha512-nBx/DMM7nCgnOzo1JyNnVaIrk/Xi5wIPNi8jixrEV6w9Om2K6dHutn/79Xzp2dQlNGSLHEDjky6N2RyFgmXh0g==}
'@lexical/plain-text@0.16.0':
resolution: {integrity: sha512-BK7/GSOZUHRJTbNPkpb9a/xN9z+FBCdunTsZhnOY8pQ7IKws3kuMO2Tk1zXfTd882ZNAxFdDKNdLYDSeufrKpw==}
'@lexical/selection@0.16.0':
resolution: {integrity: sha512-trT9gQVJ2j6AwAe7tHJ30SRuxCpV6yR9LFtggxphHsXSvJYnoHC0CXh1TF2jHl8Gd5OsdWseexGLBE4Y0V3gwQ==}
'@lexical/table@0.16.0':
resolution: {integrity: sha512-A66K779kxdr0yH2RwT2itsMnkzyFLFNPXyiWGLobCH8ON4QPuBouZvjbRHBe8Pe64yJ0c1bRDxSbTqUi9Wt3Gg==}
'@lexical/utils@0.16.0':
resolution: {integrity: sha512-GWmFEmd7o3GHqJBaEwzuZQbfTNI3Gg8ReGuHMHABgrkhZ8j2NggoRBlxsQLG0f7BewfTMVwbye22yBPq78775w==}
'@lezer/common@1.2.1':
resolution: {integrity: sha512-yemX0ZD2xS/73llMZIK6KplkjIjf2EvAHcinDi/TfJ9hS25G0388+ClHt6/3but0oOxinTcQHJLDXh6w1crzFQ==}
'@lezer/css@1.1.9':
resolution: {integrity: sha512-TYwgljcDv+YrV0MZFFvYFQHCfGgbPMR6nuqLabBdmZoFH3EP1gvw8t0vae326Ne3PszQkbXfVBjCnf3ZVCr0bA==}
'@lezer/highlight@1.2.0':
resolution: {integrity: sha512-WrS5Mw51sGrpqjlh3d4/fOwpEV2Hd3YOkp9DBt4k8XZQcoTHZFB7sx030A6OcahF4J1nDQAa3jXlTVVYH50IFA==}
'@lezer/html@1.3.10':
resolution: {integrity: sha512-dqpT8nISx/p9Do3AchvYGV3qYc4/rKr3IBZxlHmpIKam56P47RSHkSF5f13Vu9hebS1jM0HmtJIwLbWz1VIY6w==}
'@lezer/javascript@1.4.18':
resolution: {integrity: sha512-Y8BeHOt4LtcxJgXwadtfSeWPrh0XzklcCHnCVT+vOsxqH4gWmunP2ykX+VVOlM/dusyVyiNfG3lv0f10UK+mgA==}
'@lezer/json@1.0.2':
resolution: {integrity: sha512-xHT2P4S5eeCYECyKNPhr4cbEL9tc8w83SPwRC373o9uEdrvGKTZoJVAGxpOsZckMlEh9W23Pc72ew918RWQOBQ==}
'@lezer/lr@1.4.1':
resolution: {integrity: sha512-CHsKq8DMKBf9b3yXPDIU4DbH+ZJd/sJdYOW2llbW/HudP5u0VS6Bfq1hLYfgU7uAYGFIyGGQIsSOXGPEErZiJw==}
'@lezer/markdown@1.3.1':
resolution: {integrity: sha512-DGlzU/i8DC8k0uz1F+jeePrkATl0jWakauTzftMQOcbaMkHbNSRki/4E2tOzJWsVpoKYhe7iTJ03aepdwVUXUA==}
'@malept/cross-spawn-promise@1.1.1':
resolution: {integrity: sha512-RTBGWL5FWQcg9orDOCcp4LvItNzUPcyEU9bwaeJX0rJ1IQxzucC48Y0/sQLp/g6t99IQgAlGIaesJS+gTn7tVQ==}
engines: {node: '>= 10'}
'@malept/flatpak-bundler@0.4.0':
resolution: {integrity: sha512-9QOtNffcOF/c1seMCDnjckb3R9WHcG34tky+FHpNKKCW0wc/scYLwMtO+ptyGUfMW0/b/n4qRiALlaFHc9Oj7Q==}
engines: {node: '>= 10.0.0'}
'@modyfi/vite-plugin-yaml@1.1.0':
resolution: {integrity: sha512-L26xfzkSo1yamODCAtk/ipVlL6OEw2bcJ92zunyHu8zxi7+meV0zefA9xscRMDCsMY8xL3C3wi3DhMiPxcbxbw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vite: ^3.2.7 || ^4.0.5 || ^5.0.5
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@monaco-editor/loader@1.4.0':
resolution: {integrity: sha512-00ioBig0x642hytVspPl7DbQyaSWRaolYie/UFNjoTdvoKPzo6xrXLhTk9ixgIKcLH5b5vDOjVNiGyY+uDCUlg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
monaco-editor: '>= 0.21.0 < 1'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@monaco-editor/react@4.6.0':
resolution: {integrity: sha512-RFkU9/i7cN2bsq/iTkurMWOEErmYcY6JiQI3Jn+WeR/FGISH8JbHERjpS9oRuSOPvDMJI0Z8nJeKkbOs9sBYQw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
monaco-editor: '>= 0.25.0 < 1'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: ^16.8.0 || ^17.0.0 || ^18.0.0
react-dom: ^16.8.0 || ^17.0.0 || ^18.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@noble/hashes@1.4.0':
resolution: {integrity: sha512-V1JJ1WTRUqHHrOSh597hURcMqVKVGL/ea3kv0gSnEdsEZ0/+VyPghM1lMNGc00z7CIQorSvbKpuJkxvuHbvdbg==}
engines: {node: '>= 16'}
'@nodelib/fs.scandir@2.1.5':
resolution: {integrity: sha512-vq24Bq3ym5HEQm2NKCr3yXDwjc7vTsEThRDnkp2DK9p1uqLR+DHurm/NOTo0KG7HYHU7eppKZj3MyqYuMBf62g==}
engines: {node: '>= 8'}
'@nodelib/fs.stat@2.0.5':
resolution: {integrity: sha512-RkhPPp2zrqDAQA/2jNhnztcPAlv64XdhIp7a7454A5ovI7Bukxgt7MX7udwAu3zg1DcpPU0rz3VV1SeaqvY4+A==}
engines: {node: '>= 8'}
'@nodelib/fs.walk@1.2.8':
resolution: {integrity: sha512-oGB+UxlgWcgQkgwo8GcEGwemoTFt3FIO9ababBmaGwXIoBKZ+GTy0pP185beGg7Llih/NSHSV2XAs1lnznocSg==}
engines: {node: '>= 8'}
'@one-ini/wasm@0.1.1':
resolution: {integrity: sha512-XuySG1E38YScSJoMlqovLru4KTUNSjgVTIjyh7qMX6aNN5HY5Ct5LhRJdxO79JtTzKfzV/bnWpz+zquYrISsvw==}
'@open-rpc/client-js@1.8.1':
resolution: {integrity: sha512-vV+Hetl688nY/oWI9IFY0iKDrWuLdYhf7OIKI6U1DcnJV7r4gAgwRJjEr1QVYszUc0gjkHoQJzqevmXMGLyA0g==}
'@open-rpc/meta-schema@1.14.9':
resolution: {integrity: sha512-2/CbDzOVpcaSnMs28TsRv8MKJwJi0TTYFlQ6q6qobAH26oIuhYgcZooKf4l71emgntU6MMcFQCA0h4mJ4dBCdA==}
'@open-rpc/schema-utils-js@2.0.3':
resolution: {integrity: sha512-Qo1hqcTo0yJpEd9aX1ir1mJEW3TkbjGfiWaSsgVhtbQxkvLh5ddX5wVDnFikIk1Yw6YNb9Mu2U3Ra2zioN+Q9g==}
'@open-rpc/server-js@1.9.5':
resolution: {integrity: sha512-8eu/gPGzabwEynmeV/v/nB4BTBt0RnmBPeuMHTfmLb9/7rd4B2JSiPOpM5JK8Pd0aKXZKottqyS9HfFhBh5hZw==}
'@pkgjs/parseargs@0.11.0':
resolution: {integrity: sha512-+1VkjdD0QBLPodGrJUeqarH8VAIvQODIbwh9XpP5Syisf7YoQgsJKPNFoqqLQlu+VQ/tVSshMR6loPMn8U+dPg==}
engines: {node: '>=14'}
'@pkgr/core@0.1.1':
resolution: {integrity: sha512-cq8o4cWH0ibXh9VGi5P20Tu9XF/0fFXl9EUinr9QfTM7a7p0oTA4iJRCQWppXR1Pg8dSM0UCItCkPwsk9qWWYA==}
engines: {node: ^12.20.0 || ^14.18.0 || >=16.0.0}
'@playwright/test@1.45.0':
resolution: {integrity: sha512-TVYsfMlGAaxeUllNkywbwek67Ncf8FRGn8ZlRdO291OL3NjG9oMbfVhyP82HQF0CZLMrYsvesqoUekxdWuF9Qw==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@polka/url@1.0.0-next.25':
resolution: {integrity: sha512-j7P6Rgr3mmtdkeDGTe0E/aYyWEWVtc5yFXtHCRHs28/jptDEWfaVOc5T7cblqy1XKPPfCxJc/8DwQ5YgLOZOVQ==}
'@react-aria/breadcrumbs@3.5.16':
resolution: {integrity: sha512-OXLKKu4SmjnSaSHkk4kow5/aH/SzlHWPJt+Uq3xec9TwDOr/Ob8aeFVGFoY0HxfGozuQlUz+4e+d29vfA0jNWg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/button@3.9.8':
resolution: {integrity: sha512-MdbMQ3t5KSCkvKtwYd/Z6sgw0v+r1VQFRYOZ4L53xOkn+u140z8vBpNeWKZh/45gxGv7SJn9s2KstLPdCWmIxw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/calendar@3.5.11':
resolution: {integrity: sha512-VLhBovLVu3uJXBkHbgEippmo/K58QLcc/tSJQ0aJUNyHsrvPgHEcj484cb+Uj/yOirXEIzaoW6WEvhcdKrb49Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/checkbox@3.14.6':
resolution: {integrity: sha512-LICY1PR3WsW/VbuLMjZbxo75+poeo3XCXGcUnk6hxMlWfp/Iy/XHVsHlGu9stRPKRF8BSuOGteaHWVn6IXfwtA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/collections@3.0.0-alpha.4':
resolution: {integrity: sha512-chMNAlsubnpErBWN7sLhmAMOnE7o17hSfq3s0VDHlvRN9K/mPOPlYokmyWkkPqi7fYiR50EPVHDtwTWLJoqfnw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/color@3.0.0-rc.2':
resolution: {integrity: sha512-h4P7LocDEHPOEWgHYb8VPJLRGkyMhcsXemmvGao6G23zGTpTX8Nr6pEuJhcXQlGWt8hXvj/ASnC750my+zb1yA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/combobox@3.10.3':
resolution: {integrity: sha512-EdDwr2Rp1xy7yWjOYHt2qF1IpAtUrkaNKZJzlIw1XSwcqizQY6E8orNPdZr6ZwD6/tgujxF1N71JTKyffrR0Xw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/datepicker@3.11.2':
resolution: {integrity: sha512-6sbLln3VXSBcBRDgSACBzIzF/5KV5NlNOhZvXPFE6KqFw6GbevjZQTv5BNDXiwA3CQoawIRF7zgRvTANw8HkNA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/dialog@3.5.17':
resolution: {integrity: sha512-lvfEgaqg922J1hurscqCS600OZQVitGtdpo81kAefJaUzMnCxzrYviyT96aaW0simHOlimbYF5js8lxBLZJRaw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/dnd@3.7.2':
resolution: {integrity: sha512-NuE3EGqoBbe9aXAO9mDfbu4kMO7S4MCgkjkCqYi16TWfRUf38ajQbIlqodCx91b3LVN3SYvNbE3D4Tj5ebkljw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus@3.18.2':
resolution: {integrity: sha512-Jc/IY+StjA3uqN73o6txKQ527RFU7gnG5crEl5Xy3V+gbYp2O5L3ezAo/E0Ipi2cyMbG6T5Iit1IDs7hcGu8aw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/form@3.0.8':
resolution: {integrity: sha512-8S2QiyUdAgK43M3flohI0R+2rTyzH088EmgeRArA8euvJTL16cj/oSOKMEgWVihjotJ9n6awPb43ZhKboyNsMg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/grid@3.10.3':
resolution: {integrity: sha512-l0r9mz05Gwjq3t6JOTNQOf+oAoWN0bXELPJtIr8m0XyXMPFCQe1xsTaX8igVQdrDmXyBc75RAWS0BJo2JF2fIA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/gridlist@3.9.3':
resolution: {integrity: sha512-bb9GnKKeuL6NljoVUcHxr9F0cy/2WDOXRYeMikTnviRw6cuX95oojrhFfCUvz2d6ID22Btrvh7LkE+oIPVuc+g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/i18n@3.12.2':
resolution: {integrity: sha512-PvEyC6JWylTpe8dQEWqQwV6GiA+pbTxHQd//BxtMSapRW3JT9obObAnb/nFhj3HthkUvqHyj0oO1bfeN+mtD8A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/interactions@3.22.3':
resolution: {integrity: sha512-RRUb/aG+P0IKTIWikY/SylB6bIbLZeztnZY2vbe7RAG5MgVaCgn5HQ45SI15GlTmhsFG8CnF6slJsUFJiNHpbQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/label@3.7.11':
resolution: {integrity: sha512-REgejE5Qr8cXG/b8H2GhzQmjQlII/0xQW/4eDzydskaTLvA7lF5HoJUE6biYTquH5va38d8XlH465RPk+bvHzA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/link@3.7.4':
resolution: {integrity: sha512-E8SLDuS9ssm/d42+3sDFNthfMcNXMUrT2Tq1DIZt22EsMcuEzmJ9B0P7bDP5RgvIw05xVGqZ20nOpU4mKTxQtA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/listbox@3.13.3':
resolution: {integrity: sha512-htluPyDfFtn66OEYaJdIaFCYH9wGCNk30vOgZrQkPul9F9Cjce52tTyPVR0ERsf14oCUsjjS5qgeq3dGidRqEw==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/live-announcer@3.3.4':
resolution: {integrity: sha512-w8lxs35QrRrn6pBNzVfyGOeqWdxeVKf9U6bXIVwhq7rrTqRULL8jqy8RJIMfIs1s8G5FpwWYjyBOjl2g5Cu1iA==}
'@react-aria/menu@3.15.3':
resolution: {integrity: sha512-vvUmVjJwIg3h2r+7isQXTwlmoDlPAFBckHkg94p3afrT1kNOTHveTsaVl17mStx/ymIioaAi3PrIXk/PZXp1jw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/meter@3.4.16':
resolution: {integrity: sha512-hJqKnEE6mmK2Psx5kcI7NZ44OfTg0Bp7DatQSQ4zZE4yhnykRRwxqSKjze37tPR63cCqgRXtQ5LISfBfG54c0Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/numberfield@3.11.6':
resolution: {integrity: sha512-nvEWiQcWRwj6O2JXmkXEeWoBX/GVZT9zumFJcew3XknGTWJUr3h2AOymIQFt9g4mpag8IgOFEpSIlwhtZHdp1A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/overlays@3.23.2':
resolution: {integrity: sha512-vjlplr953YAuJfHiP4O+CyrTlr6OaFgXAGrzWq4MVMjnpV/PT5VRJWYFHR0sUGlHTPqeKS4NZbi/xCSgl/3pGQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/progress@3.4.16':
resolution: {integrity: sha512-RbDIFQg4+/LG+KYZeLAijt2zH7K2Gp0CY9RKWdho3nU5l3/w57Fa7NrfDGWtpImrt7bR2nRmXMA6ESfr7THfrg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/radio@3.10.7':
resolution: {integrity: sha512-o2tqIe7xd1y4HeCBQfz/sXIwLJuI6LQbVoCQ1hgk/5dGhQ0LiuXohRYitGRl9zvxW8jYdgLULmOEDt24IflE8A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/searchfield@3.7.8':
resolution: {integrity: sha512-SsF5xwH8Us548QgzivvbM7nhFbw7pu23xnRRIuhlP3MwOR3jRUFh17NKxf3Z0jvrDv/u0xfm3JKHIgaUN0KJ2A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/select@3.14.9':
resolution: {integrity: sha512-tiNgMyA2G9nKnFn3pB/lMSgidNToxSFU7r6l4OcG+Vyr63J7B/3dF2lTXq8IYhlfOR3K3uQkjroSx52CmC3NDw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/selection@3.19.3':
resolution: {integrity: sha512-GYoObXCXlmGK08hp7Qfl6Bk0U+bKP5YDWSsX+MzNjJsqzQSLm4S06tRB9ACM7gIo9dDCvL4IRxdSYTJAlJc6bw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/separator@3.4.2':
resolution: {integrity: sha512-Xql9Kg3VlGesEUC7QheE+L5b3KgBv0yxiUU+/4JP8V2vfU/XSz4xmprHEeq7KVQVOetn38iiXU8gA5g26SEsUA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/slider@3.7.11':
resolution: {integrity: sha512-2WAwjANXPsA2LHJ5nxxV4c7ihFAzz2spaBz8+FJ7MDYE7WroYnE8uAXElea1aGo+Lk0DTiAdepLpBkggqPNanw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/spinbutton@3.6.8':
resolution: {integrity: sha512-OJMAYRIZ0WrWE+5tZsywrSg4t+aOwl6vl/e1+J64YcGMM+p+AKd61KGG5T0OgNSORXjoVIZOmj6wZ6Od4xfPMw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/ssr@3.9.6':
resolution: {integrity: sha512-iLo82l82ilMiVGy342SELjshuWottlb5+VefO3jOQqQRNYnJBFpUSadswDPbRimSgJUZuFwIEYs6AabkP038fA==}
engines: {node: '>= 12'}
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/switch@3.6.7':
resolution: {integrity: sha512-yBNvKylhc3ZRQ0+7mD0mIenRRe+1yb8YaqMMZr8r3Bf87LaiFtQyhRFziq6ZitcwTJz5LEWjBihxbSVvUrf49w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/table@3.15.3':
resolution: {integrity: sha512-nQCLjlEvyJHyuijHw8ESqnA9fxNJfQHx0WPcl08VDEb8VxcE/MVzSAIedSWaqjG5k9Oflz6o/F/zHtzw4AFAow==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/tabs@3.9.5':
resolution: {integrity: sha512-aQZGAoOIg1B16qlvXIy6+rHbNBNVcWkGjOjeyvqTTPMjXt/FmElkICnqckI7MRJ1lTqzyppCOBitYOHSXRo8Uw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/tag@3.4.5':
resolution: {integrity: sha512-iyJuATQ8t2cdLC7hiZm143eeZze/MtgxaMq0OewlI9TUje54bkw2Q+CjERdgisIo3Eemf55JJgylGrTcalEJAg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/textfield@3.14.8':
resolution: {integrity: sha512-FHEvsHdE1cMR2B7rlf+HIneITrC40r201oLYbHAp3q26jH/HUujzFBB9I20qhXjyBohMWfQLqJhSwhs1VW1RJQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/toggle@3.10.7':
resolution: {integrity: sha512-/RJQU8QlPZXRElZ3Tt10F5K5STgUBUGPpfuFUGuwF3Kw3GpPxYsA1YAVjxXz2MMGwS0+y6+U/J1xIs1AF0Jwzg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/toolbar@3.0.0-beta.8':
resolution: {integrity: sha512-nMlA1KK54/Kohb3HlHAzobg69PVIEr8Q1j5P3tLd9apY8FgGvnz7yLpcj6kO1GA872gseEzgiO0Rzk+yRHQRCA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/tooltip@3.7.7':
resolution: {integrity: sha512-UOTTDbbUz7OaE48VjNSWl+XQbYCUs5Gss4I3Tv1pfRLXzVtGYXv3ur/vRayvZR0xd12ANY26fZPNkSmCFpmiXw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/tree@3.0.0-alpha.5':
resolution: {integrity: sha512-6JtkvQ/KQNFyqxc5M6JMVY63heHt2gZAwXxEt+Ojx/sbWDtDb5RrZVgkb44n7R/tMrFPJEiYZLMFPbGCsUQeJQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/utils@3.25.3':
resolution: {integrity: sha512-PR5H/2vaD8fSq0H/UB9inNbc8KDcVmW6fYAfSWkkn+OAdhTTMVKqXXrZuZBWyFfSD5Ze7VN6acr4hrOQm2bmrA==}
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/virtualizer@4.0.2':
resolution: {integrity: sha512-HNhpZl53UM2Z8g0DNvjAW7aZRwOReYgKRxdTF/IlYHNMLpdqWZinKwLbxZCsbgX3SCjdIGns90YhkMSKVpfrpw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/visually-hidden@3.8.15':
resolution: {integrity: sha512-l+sJ7xTdD5Sd6+rDNDaeJCSPnHOsI+BaJyApvb/YcVgHa7rB47lp6TXCWUCDItcPY4JqRGyeByRJVrtzBFTWCw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/calendar@3.5.4':
resolution: {integrity: sha512-R2011mtFSXIjzMXaA+CZ1sflPm9XkTBMqVk77Bnxso2ZsG7FUX8nqFmaDavxwTuHFC6OUexAGSMs8bP9KycTNg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/checkbox@3.6.8':
resolution: {integrity: sha512-c8TWjU67XHHBCpqj6+FXXhQUWGr2Pil1IKggX81pkedhWiJl3/7+WHJuZI0ivGnRjp3aISNOG8UNVlBEjS9E8A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/collections@3.10.9':
resolution: {integrity: sha512-plyrng6hOQMG8LrjArMA6ts/DgWyXln3g90/hFNbqe/hdVYF53sDVsj8Jb+5LtoYTpiAlV6eOvy1XR0vPZUf8w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/color@3.7.2':
resolution: {integrity: sha512-tNJ7pQjBqXtfASdLRjIYzeI8q0b3JtxqkJbusyEEdLAumpcWkbOvl3Vp9un0Bu/XXWihDa4v2dEdpKxjM+pPxg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/combobox@3.9.2':
resolution: {integrity: sha512-ZsbAcD58IvxZqwYxg9d2gOf8R/k5RUB2TPUiGKD6wgWfEKH6SDzY3bgRByHGOyMCyJB62cHjih/ZShizNTguqA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/data@3.11.6':
resolution: {integrity: sha512-S8q1Ejuhijl8SnyVOdDNFrMrWWnLk/Oh1ZT3KHSbTdpfMRtvhi5HukoiP06jlzz75phnpSPQL40npDtUB/kk3Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/datepicker@3.10.2':
resolution: {integrity: sha512-pa5IZUw+49AyOnddwu4XwU2kI5eo/1thbiIVNHP8uDpbbBrBkquSk3zVFDAGX1cu/I1U2VUkt64U/dxgkwaMQw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/dnd@3.4.2':
resolution: {integrity: sha512-VrHmNoNdVGrx5JHdz/zewmN+N8rlZe+vL/iAOLmvQ74RRLEz8KDFnHdlhgKg1AZqaSg3JJ18BlHEkS7oL1n+tA==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/flags@3.0.3':
resolution: {integrity: sha512-/ha7XFA0RZTQsbzSPwu3KkbNMgbvuM0GuMTYLTBWpgBrovBNTM+QqI/PfZTdHg8PwCYF4H5Y8gjdSpdulCvJFw==}
'@react-stately/form@3.0.5':
resolution: {integrity: sha512-J3plwJ63HQz109OdmaTqTA8Qhvl3gcYYK7DtgKyNP6mc/Me2Q4tl2avkWoA+22NRuv5m+J8TpBk4AVHUEOwqeQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/grid@3.9.2':
resolution: {integrity: sha512-2gK//sqAqg2Xaq6UITTFQwFUJnBRgcW+cKBVbFt+F8d152xB6UwwTS/K79E5PUkOotwqZgTEpkrSFs/aVxCLpw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/layout@4.0.2':
resolution: {integrity: sha512-g3IOrYQcaWxWKW44fYCOLoLMYKEmoOAcT9vQIbgK8MLTQV9Zgt9sGREwn4WJPm85N58Ij6yP72aQ7og/PSymvg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/list@3.10.8':
resolution: {integrity: sha512-rHCiPLXd+Ry3ztR9DkLA5FPQeH4Zd4/oJAEDWJ77W3oBBOdiMp3ZdHDLP7KBRh17XGNLO/QruYoHWAQTPiMF4g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/menu@3.8.2':
resolution: {integrity: sha512-lt6hIHmSixMzkKx1rKJf3lbAf01EmEvvIlENL20GLiU9cRbpPnPJ1aJMZ5Ad5ygglA7wAemAx+daPhlTQfF2rg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/numberfield@3.9.6':
resolution: {integrity: sha512-p2R9admGLI439qZzB39dyANhkruprJJtZwuoGVtxW/VD0ficw6BrPVqAaKG25iwKPkmveleh9p8o+yRqjGedcQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/overlays@3.6.10':
resolution: {integrity: sha512-XxZ2qScT5JPwGk9qiVJE4dtVh3AXTcYwGRA5RsHzC26oyVVsegPqY2PmNJGblAh6Q57VyodoVUyebE0Eo5CzRw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/radio@3.10.7':
resolution: {integrity: sha512-ZwGzFR+sGd42DxRlDTp3G2vLZyhMVtgHkwv2BxazPHxPMvLO9yYl7+3PPNxAmhMB4tg2u9CrzffpGX2rmEJEXA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/searchfield@3.5.6':
resolution: {integrity: sha512-gVzU0FeWiLYD8VOYRgWlk79Qn7b2eirqOnWhtI5VNuGN8WyNaCIuBp6SkXTW2dY8hs2Hzn8HlMbgy1MIc7130Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/select@3.6.7':
resolution: {integrity: sha512-hCUIddw0mPxVy1OH6jhyaDwgNea9wESjf+MYdnnTG/abRB+OZv/dWScd87OjzVsHTHWcw7CN4ZzlJoXm0FJbKQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/selection@3.16.2':
resolution: {integrity: sha512-C4eSKw7BIZHJLPzwqGqCnsyFHiUIEyryVQZTJDt6d0wYBOHU6k1pW+Q4VhrZuzSv+IMiI2RkiXeJKc55f0ZXrg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/slider@3.5.7':
resolution: {integrity: sha512-gEIGTcpBLcXixd8LYiLc8HKrBiGQJltrrEGoOvvTP8KVItXQxmeL+JiSsh8qgOoUdRRpzmAoFNUKGEg2/gtN8A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/table@3.12.2':
resolution: {integrity: sha512-dUcsrdALylhWz6exqIoqtR/dnrzjIAptMyAUPT378Y/mCYs4PxKkHSvtPEQrZhdQS1ALIIgfeg9KUVIempoXPw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/tabs@3.6.9':
resolution: {integrity: sha512-YZDqZng3HrRX+uXmg6u78x73Oi24G5ICpiXVqDKKDkO333XCA5H8MWItiuPZkYB2h3SbaCaLqSobLkvCoWYpNQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/toggle@3.7.7':
resolution: {integrity: sha512-AS+xB4+hHWa3wzYkbS6pwBkovPfIE02B9SnuYTe0stKcuejpWKo5L3QMptW0ftFYsW3ZPCXuneImfObEw2T01A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/tooltip@3.4.12':
resolution: {integrity: sha512-QKYT/cze7n9qaBsk7o5ais3jRfhYCzcVRfps+iys/W+/9FFbbhjfQG995Lwi6b+vGOHWfXxXpwmyIO2tzM1Iog==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/tree@3.8.4':
resolution: {integrity: sha512-HFNclIXJ/3QdGQWxXbj+tdlmIX/XwCfzAMB5m26xpJ6HtJhia6dtx3GLfcdyHNjmuRbAsTBsAAnnVKBmNRUdIQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/utils@3.10.4':
resolution: {integrity: sha512-gBEQEIMRh5f60KCm7QKQ2WfvhB2gLUr9b72sqUdIZ2EG+xuPgaIlCBeSicvjmjBvYZwOjoOEnmIkcx2GHp/HWw==}
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/virtualizer@4.0.2':
resolution: {integrity: sha512-LiSr6E6OoL/cKVFO088zEzkNGj41g02nlOAgLluYONncNEjoYiHmb8Yw0otPgViVLKiFjO6Kk4W+dbt8EZ51Ag==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/breadcrumbs@3.7.7':
resolution: {integrity: sha512-ZmhXwD2LLzfEA2OvOCp/QvXu8A/Edsrn5q0qUDGsmOZj9SCVeT82bIv8P+mQnATM13mi2gyoik6102Jc1OscJA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/button@3.9.6':
resolution: {integrity: sha512-8lA+D5JLbNyQikf8M/cPP2cji91aVTcqjrGpDqI7sQnaLFikM8eFR6l1ZWGtZS5MCcbfooko77ha35SYplSQvw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/calendar@3.4.9':
resolution: {integrity: sha512-O/PS9c21HgO9qzxOyZ7/dTccxabFZdF6tj3UED4DrBw7AN3KZ7JMzwzYbwHinOcO7nUcklGgNoAIHk45UAKR9g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/checkbox@3.8.3':
resolution: {integrity: sha512-f4c1mnLEt0iS1NMkyZXgT3q3AgcxzDk7w6MSONOKydcnh0xG5L2oefY14DhVDLkAuQS7jThlUFwiAs+MxiO3MA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/color@3.0.0-rc.1':
resolution: {integrity: sha512-aw6FzrBlZTWKrFaFskM7e3AFICe6JqH10wO0E919goa3LZDDFbyYEwRpatwjIyiZH1elEUkFPgwqpv3ZcPPn8g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/combobox@3.12.1':
resolution: {integrity: sha512-bd5YwHZWtgnJx4jGbplWbYzXj7IbO5w3IY5suNR7r891rx6IktquZ8GQwyYH0pQ/x+X5LdK2xI59i6+QC2PmlA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/datepicker@3.8.2':
resolution: {integrity: sha512-Ih4F0bNVGrEuwCD8XmmBAspuuOBsj/Svn/pDFtC2RyAZjXfWh+sI+n4XLz/sYKjvARh5TUI8GNy9smYS4vYXug==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/dialog@3.5.12':
resolution: {integrity: sha512-JmpQbSpXltqEyYfEwoqDolABIiojeExkqolHNdQlayIsfFuSxZxNwXZPOpz58Ri/iwv21JP7K3QF0Gb2Ohxl9w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/form@3.7.6':
resolution: {integrity: sha512-lhS2y1bVtRnyYjkM+ylJUp2g663ZNbeZxu2o+mFfD5c2wYmVLA58IWR90c7DL8IVUitoANnZ1JPhhXvutiFpQQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/grid@3.2.8':
resolution: {integrity: sha512-6PJrpukwMqlv3IhJSDkJuVbhHM8Oe6hd2supWqd9adMXrlSP7QHt9a8SgFcFblCCTx8JzUaA0PvY5sTudcEtOQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/link@3.5.7':
resolution: {integrity: sha512-2WyaVmm1qr9UrSG3Dq6iz+2ziuVp+DH8CsYZ9CA6aNNb6U18Hxju3LTPb4a5gM0eC7W0mQGNBmrgGlAdDZEJOw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/listbox@3.5.1':
resolution: {integrity: sha512-n5bOgD9lgfK1qaLtag9WPnu151SwXBCNn/OgGY/Br9mWRl+nPUEYtFcPX+2VCld7uThf54kwrTmzlFnaraIlcw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/menu@3.9.11':
resolution: {integrity: sha512-IguQVF70d7aHXgWB1Rd2a/PiIuLZ2Nt7lyayJshLcy/NLOYmgpTmTyn2WCtlA5lTfQwmQrNFf4EvnWkeljJXdA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/meter@3.4.3':
resolution: {integrity: sha512-Y2fX5CTAPGRKxVSeepbeyN6/K+wlF9pMRcNxTSU2qDwdoFqNCtTWMcWuCsU/Y2L/zU0jFWu4x0Vo7WkrcsgcMA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/numberfield@3.8.5':
resolution: {integrity: sha512-LVWggkxwd1nyVZomXBPfQA1E4I4/i4PBifjcDs2AfcV7q5RE9D+DVIDXsYucVOBxPlDOxiAq/T9ypobspWSwHw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/overlays@3.8.9':
resolution: {integrity: sha512-9ni9upQgXPnR+K9cWmbYWvm3ll9gH8P/XsEZprqIV5zNLMF334jADK48h4jafb1X9RFnj0WbHo6BqcSObzjTig==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/progress@3.5.6':
resolution: {integrity: sha512-Nh43sjQ5adyN1bTHBPRaIPhXUdBqP0miYeJpeMY3V/KUl4qmouJLwDnccwFG4xLm6gBfYe22lgbbV7nAfNnuTQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/radio@3.8.3':
resolution: {integrity: sha512-fUVJt4Bb6jOReFqnhHVNxWXH7t6c60uSFfoPKuXt/xI9LL1i2jhpur0ggpTfIn3qLIAmNBU6bKBCWAdr4KjeVQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/searchfield@3.5.8':
resolution: {integrity: sha512-EcdqalHNIC6BJoRfmqUhAvXRd3aHkWlV1cFCz57JJKgUEFYyXPNrXd1b73TKLzTXEk+X/D6LKV15ILYpEaxu8w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/select@3.9.6':
resolution: {integrity: sha512-cVSFR0eJLup/ht1Uto+y8uyLmHO89J6wNh65SIHb3jeVz9oLBAedP3YNI2qB+F9qFMUcA8PBSLXIIuT6gXzLgQ==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared@3.25.0':
resolution: {integrity: sha512-OZSyhzU6vTdW3eV/mz5i6hQwQUhkRs7xwY2d1aqPvTdMe0+2cY7Fwp45PAiwYLEj73i9ro2FxF9qC4DvHGSCgQ==}
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/slider@3.7.5':
resolution: {integrity: sha512-bRitwQRQjQoOcKEdPMljnvm474dwrmsc6pdsVQDh/qynzr+KO9IHuYc3qPW53WVE2hMQJDohlqtCAWQXWQ5Vcg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/switch@3.5.5':
resolution: {integrity: sha512-SZx1Bd+COhAOs/RTifbZG+uq/llwba7VAKx7XBeX4LeIz1dtguy5bigOBgFTMQi4qsIVCpybSWEEl+daj4XFPw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/table@3.10.1':
resolution: {integrity: sha512-xsNh0Gm4GtNeSknZqkMsfGvc94fycmfhspGO+FzQKim2hB5k4yILwd+lHYQ2UKW6New9GVH/zN2Pd3v67IeZ2g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/tabs@3.3.9':
resolution: {integrity: sha512-3Q9kRVvg/qDyeJR/W1+C2z2OyvDWQrSLvOCvAezX5UKzww4rBEAA8OqBlyDwn7q3fiwrh/m64l6p+dbln+RdxQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/textfield@3.9.6':
resolution: {integrity: sha512-0uPqjJh4lYp1aL1HL9IlV8Cgp8eT0PcsNfdoCktfkLytvvBPmox2Pfm57W/d0xTtzZu2CjxhYNTob+JtGAOeXA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/tooltip@3.4.11':
resolution: {integrity: sha512-WPikHQxeT5Lb09yJEaW6Ja3ecE0g1YM6ukWYS2v/iZLUPn5YlYrGytspuCYQNSh/u7suCz4zRLEHYCl7OCigjw==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@remix-run/router@1.17.0':
resolution: {integrity: sha512-2D6XaHEVvkCn682XBnipbJjgZUU7xjLtA4dGJRBVUKpEaDYOZMENZoZjAOSb7qirxt5RupjzZxz4fK2FO+EFPw==}
engines: {node: '>=14.0.0'}
'@rollup/pluginutils@5.1.0':
resolution: {integrity: sha512-XTIWOPPcpvyKI6L1NHo0lFlCyznUEyPmPY1mc3KpPVDYulHSTvyeLNVW00QTLIAFNhR3kYnJTQHeGqU4M3n09g==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
rollup: ^1.20.0||^2.0.0||^3.0.0||^4.0.0
peerDependenciesMeta:
rollup:
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-android-arm-eabi@4.24.0':
resolution: {integrity: sha512-Q6HJd7Y6xdB48x8ZNVDOqsbh2uByBhgK8PiQgPhwkIw/HC/YX5Ghq2mQY5sRMZWHb3VsFkWooUVOZHKr7DmDIA==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [arm]
os: [android]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-android-arm64@4.24.0':
resolution: {integrity: sha512-ijLnS1qFId8xhKjT81uBHuuJp2lU4x2yxa4ctFPtG+MqEE6+C5f/+X/bStmxapgmwLwiL3ih122xv8kVARNAZA==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [arm64]
os: [android]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-darwin-arm64@4.24.0':
resolution: {integrity: sha512-bIv+X9xeSs1XCk6DVvkO+S/z8/2AMt/2lMqdQbMrmVpgFvXlmde9mLcbQpztXm1tajC3raFDqegsH18HQPMYtA==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [arm64]
os: [darwin]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-darwin-x64@4.24.0':
resolution: {integrity: sha512-X6/nOwoFN7RT2svEQWUsW/5C/fYMBe4fnLK9DQk4SX4mgVBiTA9h64kjUYPvGQ0F/9xwJ5U5UfTbl6BEjaQdBQ==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [x64]
os: [darwin]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-arm-gnueabihf@4.24.0':
resolution: {integrity: sha512-0KXvIJQMOImLCVCz9uvvdPgfyWo93aHHp8ui3FrtOP57svqrF/roSSR5pjqL2hcMp0ljeGlU4q9o/rQaAQ3AYA==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [arm]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-arm-musleabihf@4.24.0':
resolution: {integrity: sha512-it2BW6kKFVh8xk/BnHfakEeoLPv8STIISekpoF+nBgWM4d55CZKc7T4Dx1pEbTnYm/xEKMgy1MNtYuoA8RFIWw==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [arm]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-arm64-gnu@4.24.0':
resolution: {integrity: sha512-i0xTLXjqap2eRfulFVlSnM5dEbTVque/3Pi4g2y7cxrs7+a9De42z4XxKLYJ7+OhE3IgxvfQM7vQc43bwTgPwA==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [arm64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-arm64-musl@4.24.0':
resolution: {integrity: sha512-9E6MKUJhDuDh604Qco5yP/3qn3y7SLXYuiC0Rpr89aMScS2UAmK1wHP2b7KAa1nSjWJc/f/Lc0Wl1L47qjiyQw==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [arm64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-powerpc64le-gnu@4.24.0':
resolution: {integrity: sha512-2XFFPJ2XMEiF5Zi2EBf4h73oR1V/lycirxZxHZNc93SqDN/IWhYYSYj8I9381ikUFXZrz2v7r2tOVk2NBwxrWw==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [ppc64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-riscv64-gnu@4.24.0':
resolution: {integrity: sha512-M3Dg4hlwuntUCdzU7KjYqbbd+BLq3JMAOhCKdBE3TcMGMZbKkDdJ5ivNdehOssMCIokNHFOsv7DO4rlEOfyKpg==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [riscv64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-s390x-gnu@4.24.0':
resolution: {integrity: sha512-mjBaoo4ocxJppTorZVKWFpy1bfFj9FeCMJqzlMQGjpNPY9JwQi7OuS1axzNIk0nMX6jSgy6ZURDZ2w0QW6D56g==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [s390x]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-x64-gnu@4.24.0':
resolution: {integrity: sha512-ZXFk7M72R0YYFN5q13niV0B7G8/5dcQ9JDp8keJSfr3GoZeXEoMHP/HlvqROA3OMbMdfr19IjCeNAnPUG93b6A==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [x64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-x64-musl@4.24.0':
resolution: {integrity: sha512-w1i+L7kAXZNdYl+vFvzSZy8Y1arS7vMgIy8wusXJzRrPyof5LAb02KGr1PD2EkRcl73kHulIID0M501lN+vobQ==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [x64]
os: [linux]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-win32-arm64-msvc@4.24.0':
resolution: {integrity: sha512-VXBrnPWgBpVDCVY6XF3LEW0pOU51KbaHhccHw6AS6vBWIC60eqsH19DAeeObl+g8nKAz04QFdl/Cefta0xQtUQ==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [arm64]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-win32-ia32-msvc@4.24.0':
resolution: {integrity: sha512-xrNcGDU0OxVcPTH/8n/ShH4UevZxKIO6HJFK0e15XItZP2UcaiLFd5kiX7hJnqCbSztUF8Qot+JWBC/QXRPYWQ==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [ia32]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-win32-x64-msvc@4.24.0':
resolution: {integrity: sha512-fbMkAF7fufku0N2dE5TBXcNlg0pt0cJue4xBRE2Qc5Vqikxr4VCgKj/ht6SMdFcOacVA9rqF70APJ8RN/4vMJw==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
cpu: [x64]
os: [win32]
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry-internal/feedback@7.118.0':
resolution: {integrity: sha512-IYOGRcqIqKJJpMwBBv+0JTu0FPpXnakJYvOx/XEa/SNyF5+l7b9gGEjUVWh1ok50kTLW/XPnpnXNAGQcoKHg+w==}
engines: {node: '>=12'}
'@sentry-internal/replay-canvas@7.118.0':
resolution: {integrity: sha512-XxHlCClvrxmVKpiZetFYyiBaPQNiojoBGFFVgbbWBIAPc+fWeLJ2BMoQEBjn/0NA/8u8T6lErK5YQo/eIx9+XQ==}
engines: {node: '>=12'}
'@sentry-internal/tracing@7.118.0':
resolution: {integrity: sha512-dERAshKlQLrBscHSarhHyUeGsu652bDTUN1FK0m4e3X48M3I5/s+0N880Qjpe5MprNLcINlaIgdQ9jkisvxjfw==}
engines: {node: '>=8'}
'@sentry/browser@7.118.0':
resolution: {integrity: sha512-8onDOFV1VLEoBuqA5yaJeR3FF1JNuxr5C7p1oN3OwY724iTVqQnOLmZKZaSnHV3RkY67wKDGQkQIie14sc+42g==}
engines: {node: '>=8'}
'@sentry/core@7.118.0':
resolution: {integrity: sha512-ol0xBdp3/K11IMAYSQE0FMxBOOH9hMsb/rjxXWe0hfM5c72CqYWL3ol7voPci0GELJ5CZG+9ImEU1V9r6gK64g==}
engines: {node: '>=8'}
'@sentry/integrations@7.118.0':
resolution: {integrity: sha512-C2rR4NvIMjokF8jP5qzSf1o2zxDx7IeYnr8u15Kb2+HdZtX559owALR0hfgwnfeElqMhGlJBaKUWZ48lXJMzCQ==}
engines: {node: '>=8'}
'@sentry/react@7.118.0':
resolution: {integrity: sha512-oEYe5TGk8S7YzPsFqDf4xDHjfzs35/QFE+dou3S2d24OYpso8Tq4C5f1VzYmnOOyy85T7JNicYLSo0n0NSJvQg==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
react: 15.x || 16.x || 17.x || 18.x
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/replay@7.118.0':
resolution: {integrity: sha512-boQfCL+1L/tSZ9Huwi00+VtU+Ih1Lcg8HtxBuAsBCJR9pQgUL5jp7ECYdTeeHyCh/RJO7JqV1CEoGTgohe10mA==}
engines: {node: '>=12'}
'@sentry/types@7.118.0':
resolution: {integrity: sha512-2drqrD2+6kgeg+W/ycmiti3G4lJrV3hGjY9PpJ3bJeXrh6T2+LxKPzlgSEnKFaeQWkXdZ4eaUbtTXVebMjb5JA==}
engines: {node: '>=8'}
'@sentry/utils@7.118.0':
resolution: {integrity: sha512-43qItc/ydxZV1Zb3Kn2M54RwL9XXFa3IAYBO8S82Qvq5YUYmU2AmJ1jgg7DabXlVSWgMA1HntwqnOV3JLaEnTQ==}
engines: {node: '>=8'}
'@shaderfrog/glsl-parser@2.1.5':
resolution: {integrity: sha512-fw7U8Y7BBV9NZVLs7lyM8lpQ9YUK7XBNJjN4HhkY3nqkKpSiIQ62PVtPYtW7uZME5072QXQNQBhHJzG3t+NH0w==}
engines: {node: '>=16'}
'@sinclair/typebox@0.27.8':
resolution: {integrity: sha512-+Fj43pSMwJs4KRrH/938Uf+uAELIgVBmQzg/q1YG10djyfA3TnrU8N8XzqCh/okZdszqBQTZf96idMfE5lnwTA==}
'@sindresorhus/is@4.6.0':
resolution: {integrity: sha512-t09vSN3MdfsyCHoFcTRCH/iUtG7OJ0CsjzB8cjAmKc/va/kIgeDI/TxsigdncE/4be734m0cvIYwNaV4i2XqAw==}
engines: {node: '>=10'}
'@smithy/is-array-buffer@2.2.0':
resolution: {integrity: sha512-GGP3O9QFD24uGeAXYUjwSTXARoqpZykHadOmA8G5vfJPK0/DC67qa//0qvqrJzL1xc8WQWX7/yc7fwudjPHPhA==}
engines: {node: '>=14.0.0'}
'@smithy/types@3.3.0':
resolution: {integrity: sha512-IxvBBCTFDHbVoK7zIxqA1ZOdc4QfM5HM7rGleCuHi7L1wnKv5Pn69xXJQ9hgxH60ZVygH9/JG0jRgtUncE3QUA==}
engines: {node: '>=16.0.0'}
'@smithy/util-buffer-from@2.2.0':
resolution: {integrity: sha512-IJdWBbTcMQ6DA0gdNhh/BwrLkDR+ADW5Kr1aZmd4k3DIF6ezMV4R2NIAmT08wQJ3yUK82thHWmC/TnK/wpMMIA==}
engines: {node: '>=14.0.0'}
'@smithy/util-utf8@2.3.0':
resolution: {integrity: sha512-R8Rdn8Hy72KKcebgLiv8jQcQkXoLMOGGv5uI1/k0l+snqkOzQ1R0ChUBCxWMlBsFMekWjq0wRudIweFs7sKT5A==}
engines: {node: '>=14.0.0'}
'@stripe/react-stripe-js@2.7.2':
resolution: {integrity: sha512-OCvSr/wMt2GUVwEW2nvRYVvv5Pkey6YQBOevYSx7N0JyuRK8yK7KtedTty7enFNnEk1dFQNppcjofz6V1i5rXA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@stripe/stripe-js': ^1.44.1 || ^2.0.0 || ^3.0.0 || ^4.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: ^16.8.0 || ^17.0.0 || ^18.0.0
react-dom: ^16.8.0 || ^17.0.0 || ^18.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@stripe/stripe-js@3.5.0':
resolution: {integrity: sha512-pKS3wZnJoL1iTyGBXAvCwduNNeghJHY6QSRSNNvpYnrrQrLZ6Owsazjyynu0e0ObRgks0i7Rv+pe2M7/MBTZpQ==}
engines: {node: '>=12.16'}
'@swc/helpers@0.5.12':
resolution: {integrity: sha512-KMZNXiGibsW9kvZAO1Pam2JPTDBm+KSHMMHWdsyI/1DbIZjT2A6Gy3hblVXUMEDvUAKq+e0vL0X0o54owWji7g==}
'@szmarczak/http-timer@4.0.6':
resolution: {integrity: sha512-4BAffykYOgO+5nzBWYwE3W90sBgLJoUPRWWcL8wlyiM8IB8ipJz3UMJ9KXQd1RKQXpKp8Tutn80HZtWsu2u76w==}
engines: {node: '>=10'}
'@tanstack/match-sorter-utils@8.15.1':
resolution: {integrity: sha512-PnVV3d2poenUM31ZbZi/yXkBu3J7kd5k2u51CGwwNojag451AjTH9N6n41yjXz2fpLeewleyLBmNS6+HcGDlXw==}
engines: {node: '>=12'}
'@tanstack/query-core@5.54.1':
resolution: {integrity: sha512-hKS+WRpT5zBFip21pB6Jx1C0hranWQrbv5EJ7qPoiV5MYI3C8rTCqWC9DdBseiPT1JgQWh8Y55YthuYZNiw3Xw==}
'@tanstack/query-devtools@5.37.1':
resolution: {integrity: sha512-XcG4IIHIv0YQKrexTqo2zogQWR1Sz672tX2KsfE9kzB+9zhx44vRKH5si4WDILE1PIWQpStFs/NnrDQrBAUQpg==}
'@tanstack/query-persist-client-core@5.54.1':
resolution: {integrity: sha512-qmBkrC5HA3XHwwrx/pWjegncQFcmuoAaffwbrXm07OrsOxxeTGLt8aFl8RYbWAs75a8+9uneqVFQfgv5QRqxBA==}
'@tanstack/react-query-devtools@5.45.1':
resolution: {integrity: sha512-4mrbk1g5jqlqh0pifZNsKzy7FtgeqgwzMICL4d6IJGayrrcrKq9K4N/OzRNbgRWrTn6YTY63qcAcKo+NJU2QMw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/react-query': ^5.45.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: ^18 || ^19
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/react-query@5.55.0':
resolution: {integrity: sha512-2uYuxEbRQD8TORUiTUacEOwt1e8aoSqUOJFGY5TUrh6rQ3U85zrMS2wvbNhBhXGh6Vj69QDCP2yv8tIY7joo6Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
react: ^18 || ^19
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/vue-query@5.54.2':
resolution: {integrity: sha512-GYIYee9WkUbPDD28t1kdNNtLCioiIva0MhKCvODGWoEML5MNONCX4/i4y2GGFi8i9nSbcA8MpvD+nt/tdZ+yJw==}
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/composition-api': ^1.1.2
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
vue: ^2.6.0 || ^3.3.0
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/composition-api':
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tootallnate/once@2.0.0':
resolution: {integrity: sha512-XCuKFP5PS55gnMVu3dty8KPatLqUoy/ZYzDzAGCQ8JNFCkLXzmI7vNHCR+XpbZaMWQK/vQubr7PkYq8g470J/A==}
engines: {node: '>= 10'}
'@tsconfig/node20@20.1.4':
resolution: {integrity: sha512-sqgsT69YFeLWf5NtJ4Xq/xAF8p4ZQHlmGW74Nu2tD4+g5fAsposc4ZfaaPixVu4y01BEiDCWLRDCvDM5JOsRxg==}
'@types/babel__core@7.20.5':
resolution: {integrity: sha512-qoQprZvz5wQFJwMDqeseRXWv3rqMvhgpbXFfVyWhbx9X47POIA6i/+dXefEmZKoAgOaTdaIgNSMqMIU61yRyzA==}
'@types/babel__generator@7.6.8':
resolution: {integrity: sha512-ASsj+tpEDsEiFr1arWrlN6V3mdfjRMZt6LtK/Vp/kreFLnr5QH5+DhvD5nINYZXzwJvXeGq+05iUXcAzVrqWtw==}
'@types/babel__template@7.4.4':
resolution: {integrity: sha512-h/NUaSyG5EyxBIp8YRxo4RMe2/qQgvyowRwVMzhYhBCONbW8PUsg4lkFMrhgZhUe5z3L3MiLDuvyJ/CaPa2A8A==}
'@types/babel__traverse@7.20.6':
resolution: {integrity: sha512-r1bzfrm0tomOI8g1SzvCaQHo6Lcv6zu0EA+W2kHrt8dyrHQxGzBBL4kdkzIS+jBMV+EYcMAEAqXqYaLJq5rOZg==}
'@types/cacheable-request@6.0.3':
resolution: {integrity: sha512-IQ3EbTzGxIigb1I3qPZc1rWJnH0BmSKv5QYTalEwweFvyBDLSAe24zP0le/hyi7ecGfZVlIVAg4BZqb8WBwKqw==}
'@types/cookie@0.3.3':
resolution: {integrity: sha512-LKVP3cgXBT9RYj+t+9FDKwS5tdI+rPBXaNSkma7hvqy35lc7mAokC2zsqWJH0LaqIt3B962nuYI77hsJoT1gow==}
'@types/css.escape@1.5.2':
resolution: {integrity: sha512-sq0h0y8i83T20MB434AZWgK3byezbBG48jllitFpVXlPOjHc5RNs3bg6rUen/EtMUjM4ZJjD4x+0aik9AXqLdQ==}
'@types/culori@2.1.1':
resolution: {integrity: sha512-NzLYD0vNHLxTdPp8+RlvGbR2NfOZkwxcYGFwxNtm+WH2NuUNV8785zv1h0sulFQ5aFQ9n/jNDUuJeo3Bh7+oFA==}
'@types/d3-array@3.2.1':
resolution: {integrity: sha512-Y2Jn2idRrLzUfAKV2LyRImR+y4oa2AntrgID95SHJxuMUrkNXmanDSed71sRNZysveJVt1hLLemQZIady0FpEg==}
'@types/d3-axis@3.0.6':
resolution: {integrity: sha512-pYeijfZuBd87T0hGn0FO1vQ/cgLk6E1ALJjfkC0oJ8cbwkZl3TpgS8bVBLZN+2jjGgg38epgxb2zmoGtSfvgMw==}
'@types/d3-brush@3.0.6':
resolution: {integrity: sha512-nH60IZNNxEcrh6L1ZSMNA28rj27ut/2ZmI3r96Zd+1jrZD++zD3LsMIjWlvg4AYrHn/Pqz4CF3veCxGjtbqt7A==}
'@types/d3-chord@3.0.6':
resolution: {integrity: sha512-LFYWWd8nwfwEmTZG9PfQxd17HbNPksHBiJHaKuY1XeqscXacsS2tyoo6OdRsjf+NQYeB6XrNL3a25E3gH69lcg==}
'@types/d3-color@3.1.3':
resolution: {integrity: sha512-iO90scth9WAbmgv7ogoq57O9YpKmFBbmoEoCHDB2xMBY0+/KVrqAaCDyCE16dUspeOvIxFFRI+0sEtqDqy2b4A==}
'@types/d3-contour@3.0.6':
resolution: {integrity: sha512-BjzLgXGnCWjUSYGfH1cpdo41/hgdWETu4YxpezoztawmqsvCeep+8QGfiY6YbDvfgHz/DkjeIkkZVJavB4a3rg==}
'@types/d3-delaunay@6.0.4':
resolution: {integrity: sha512-ZMaSKu4THYCU6sV64Lhg6qjf1orxBthaC161plr5KuPHo3CNm8DTHiLw/5Eq2b6TsNP0W0iJrUOFscY6Q450Hw==}
'@types/d3-dispatch@3.0.6':
resolution: {integrity: sha512-4fvZhzMeeuBJYZXRXrRIQnvUYfyXwYmLsdiN7XXmVNQKKw1cM8a5WdID0g1hVFZDqT9ZqZEY5pD44p24VS7iZQ==}
'@types/d3-drag@3.0.7':
resolution: {integrity: sha512-HE3jVKlzU9AaMazNufooRJ5ZpWmLIoc90A37WU2JMmeq28w1FQqCZswHZ3xR+SuxYftzHq6WU6KJHvqxKzTxxQ==}
'@types/d3-dsv@3.0.7':
resolution: {integrity: sha512-n6QBF9/+XASqcKK6waudgL0pf/S5XHPPI8APyMLLUHd8NqouBGLsU8MgtO7NINGtPBtk9Kko/W4ea0oAspwh9g==}
'@types/d3-ease@3.0.2':
resolution: {integrity: sha512-NcV1JjO5oDzoK26oMzbILE6HW7uVXOHLQvHshBUW4UMdZGfiY6v5BeQwh9a9tCzv+CeefZQHJt5SRgK154RtiA==}
'@types/d3-fetch@3.0.7':
resolution: {integrity: sha512-fTAfNmxSb9SOWNB9IoG5c8Hg6R+AzUHDRlsXsDZsNp6sxAEOP0tkP3gKkNSO/qmHPoBFTxNrjDprVHDQDvo5aA==}
'@types/d3-force@3.0.10':
resolution: {integrity: sha512-ZYeSaCF3p73RdOKcjj+swRlZfnYpK1EbaDiYICEEp5Q6sUiqFaFQ9qgoshp5CzIyyb/yD09kD9o2zEltCexlgw==}
'@types/d3-format@3.0.4':
resolution: {integrity: sha512-fALi2aI6shfg7vM5KiR1wNJnZ7r6UuggVqtDA+xiEdPZQwy/trcQaHnwShLuLdta2rTymCNpxYTiMZX/e09F4g==}
'@types/d3-geo@3.1.0':
resolution: {integrity: sha512-856sckF0oP/diXtS4jNsiQw/UuK5fQG8l/a9VVLeSouf1/PPbBE1i1W852zVwKwYCBkFJJB7nCFTbk6UMEXBOQ==}
'@types/d3-hierarchy@3.1.7':
resolution: {integrity: sha512-tJFtNoYBtRtkNysX1Xq4sxtjK8YgoWUNpIiUee0/jHGRwqvzYxkq0hGVbbOGSz+JgFxxRu4K8nb3YpG3CMARtg==}
'@types/d3-interpolate@3.0.4':
resolution: {integrity: sha512-mgLPETlrpVV1YRJIglr4Ez47g7Yxjl1lj7YKsiMCb27VJH9W8NVM6Bb9d8kkpG/uAQS5AmbA48q2IAolKKo1MA==}
'@types/d3-path@3.1.0':
resolution: {integrity: sha512-P2dlU/q51fkOc/Gfl3Ul9kicV7l+ra934qBFXCFhrZMOL6du1TM0pm1ThYvENukyOn5h9v+yMJ9Fn5JK4QozrQ==}
'@types/d3-polygon@3.0.2':
resolution: {integrity: sha512-ZuWOtMaHCkN9xoeEMr1ubW2nGWsp4nIql+OPQRstu4ypeZ+zk3YKqQT0CXVe/PYqrKpZAi+J9mTs05TKwjXSRA==}
'@types/d3-quadtree@3.0.6':
resolution: {integrity: sha512-oUzyO1/Zm6rsxKRHA1vH0NEDG58HrT5icx/azi9MF1TWdtttWl0UIUsjEQBBh+SIkrpd21ZjEv7ptxWys1ncsg==}
'@types/d3-random@3.0.3':
resolution: {integrity: sha512-Imagg1vJ3y76Y2ea0871wpabqp613+8/r0mCLEBfdtqC7xMSfj9idOnmBYyMoULfHePJyxMAw3nWhJxzc+LFwQ==}
'@types/d3-scale-chromatic@3.0.3':
resolution: {integrity: sha512-laXM4+1o5ImZv3RpFAsTRn3TEkzqkytiOY0Dz0sq5cnd1dtNlk6sHLon4OvqaiJb28T0S/TdsBI3Sjsy+keJrw==}
'@types/d3-scale@4.0.8':
resolution: {integrity: sha512-gkK1VVTr5iNiYJ7vWDI+yUFFlszhNMtVeneJ6lUTKPjprsvLLI9/tgEGiXJOnlINJA8FyA88gfnQsHbybVZrYQ==}
'@types/d3-selection@3.0.10':
resolution: {integrity: sha512-cuHoUgS/V3hLdjJOLTT691+G2QoqAjCVLmr4kJXR4ha56w1Zdu8UUQ5TxLRqudgNjwXeQxKMq4j+lyf9sWuslg==}
'@types/d3-shape@3.1.6':
resolution: {integrity: sha512-5KKk5aKGu2I+O6SONMYSNflgiP0WfZIQvVUMan50wHsLG1G94JlxEVnCpQARfTtzytuY0p/9PXXZb3I7giofIA==}
'@types/d3-time-format@4.0.3':
resolution: {integrity: sha512-5xg9rC+wWL8kdDj153qZcsJ0FWiFt0J5RB6LYUNZjwSnesfblqrI/bJ1wBdJ8OQfncgbJG5+2F+qfqnqyzYxyg==}
'@types/d3-time@3.0.3':
resolution: {integrity: sha512-2p6olUZ4w3s+07q3Tm2dbiMZy5pCDfYwtLXXHUnVzXgQlZ/OyPtUz6OL382BkOuGlLXqfT+wqv8Fw2v8/0geBw==}
'@types/d3-timer@3.0.2':
resolution: {integrity: sha512-Ps3T8E8dZDam6fUyNiMkekK3XUsaUEik+idO9/YjPtfj2qruF8tFBXS7XhtE4iIXBLxhmLjP3SXpLhVf21I9Lw==}
'@types/d3-transition@3.0.8':
resolution: {integrity: sha512-ew63aJfQ/ms7QQ4X7pk5NxQ9fZH/z+i24ZfJ6tJSfqxJMrYLiK01EAs2/Rtw/JreGUsS3pLPNV644qXFGnoZNQ==}
'@types/d3-zoom@3.0.8':
resolution: {integrity: sha512-iqMC4/YlFCSlO8+2Ii1GGGliCAY4XdeG748w5vQUbevlbDu0zSjH/+jojorQVBK/se0j6DUFNPBGSqD3YWYnDw==}
'@types/d3@7.4.3':
resolution: {integrity: sha512-lZXZ9ckh5R8uiFVt8ogUNf+pIrK4EsWrx2Np75WvF/eTpJ0FMHNhjXk8CKEx/+gpHbNQyJWehbFaTvqmHWB3ww==}
'@types/debug@4.1.12':
resolution: {integrity: sha512-vIChWdVG3LG1SMxEvI/AK+FWJthlrqlTu7fbrlywTkkaONwk/UAGaULXRlf8vkzFBLVm0zkMdCquhL5aOjhXPQ==}
'@types/eslint@8.56.10':
resolution: {integrity: sha512-Shavhk87gCtY2fhXDctcfS3e6FdxWkCx1iUZ9eEUbh7rTqlZT0/IzOkCOVt0fCjcFuZ9FPYfuezTBImfHCDBGQ==}
'@types/estree@1.0.6':
resolution: {integrity: sha512-AYnb1nQyY49te+VRAVgmzfcgjYS91mY5P0TKUDCLEM+gNnA+3T6rWITXRLYCpahpqSQbN5cE+gHpnPyXjHWxcw==}
'@types/flexsearch@0.7.6':
resolution: {integrity: sha512-H5IXcRn96/gaDmo+rDl2aJuIJsob8dgOXDqf8K0t8rWZd1AFNaaspmRsElESiU+EWE33qfbFPgI0OC/B1g9FCA==}
'@types/fs-extra@9.0.13':
resolution: {integrity: sha512-nEnwB++1u5lVDM2UI4c1+5R+FYaKfaAzS4OococimjVm3nQw3TuzH5UNsocrcTBbhnerblyHj4A49qXbIiZdpA==}
'@types/geojson@7946.0.14':
resolution: {integrity: sha512-WCfD5Ht3ZesJUsONdhvm84dmzWOiOzOAqOncN0++w0lBw1o8OuDNJF2McvvCef/yBqb/HYRahp1BYtODFQ8bRg==}
'@types/hammerjs@2.0.45':
resolution: {integrity: sha512-qkcUlZmX6c4J8q45taBKTL3p+LbITgyx7qhlPYOdOHZB7B31K0mXbP5YA7i7SgDeEGuI9MnumiKPEMrxg8j3KQ==}
'@types/hash-sum@1.0.2':
resolution: {integrity: sha512-UP28RddqY8xcU0SCEp9YKutQICXpaAq9N8U2klqF5hegGha7KzTOL8EdhIIV3bOSGBzjEpN9bU/d+nNZBdJYVw==}
'@types/http-cache-semantics@4.0.4':
resolution: {integrity: sha512-1m0bIFVc7eJWyve9S0RnuRgcQqF/Xd5QsUZAZeQFr1Q3/p9JWoQQEqmVy+DPTNpGXwhgIetAoYF8JSc33q29QA==}
'@types/jsdom@21.1.7':
resolution: {integrity: sha512-yOriVnggzrnQ3a9OKOCxaVuSug3w3/SbOj5i7VwXWZEyUNl3bLF9V3MfxGbZKuwqJOQyRfqXyROBB1CoZLFWzA==}
'@types/json-schema@7.0.15':
resolution: {integrity: sha512-5+fP8P8MFNC+AyZCDxrB2pkZFPGzqQWUzpSeuuVLvm8VMcorNYavBqoFcxK8bQz4Qsbn4oUEEem4wDLfcysGHA==}
'@types/keyv@3.1.4':
resolution: {integrity: sha512-BQ5aZNSCpj7D6K2ksrRCTmKRLEpnPvWDiLPfoGyhZ++8YtiK9d/3DBKPJgry359X/P1PfruyYwvnvwFjuEiEIg==}
'@types/linkify-it@5.0.0':
resolution: {integrity: sha512-sVDA58zAw4eWAffKOaQH5/5j3XeayukzDk+ewSsnv3p4yJEZHCCzMDiZM8e0OUrRvmpGZ85jf4yDHkHsgBNr9Q==}
'@types/mapbox-gl@2.7.21':
resolution: {integrity: sha512-Dx9MuF2kKgT/N22LsMUB4b3acFZh9clVqz9zv1fomoiPoBrJolwYxpWA/9LPO/2N0xWbKi4V+pkjTaFkkx/4wA==}
'@types/markdown-it@12.2.3':
resolution: {integrity: sha512-GKMHFfv3458yYy+v/N8gjufHO6MSZKCOXpZc5GXIWWy8uldwfmPn98vp81gZ5f9SVw8YYBctgfJ22a2d7AOMeQ==}
'@types/mdurl@2.0.0':
resolution: {integrity: sha512-RGdgjQUZba5p6QEFAVx2OGb8rQDL/cPRG7GiedRzMcJ1tYnUANBncjbSB1NRGwbvjcPeikRABz2nshyPk1bhWg==}
'@types/mime-types@2.1.4':
resolution: {integrity: sha512-lfU4b34HOri+kAY5UheuFMWPDOI+OPceBSHZKp69gEyTL/mmJ4cnU6Y/rlme3UL3GyOn6Y42hyIEw0/q8sWx5w==}
'@types/ms@0.7.34':
resolution: {integrity: sha512-nG96G3Wp6acyAgJqGasjODb+acrI7KltPiRxzHPXnP3NgI28bpQDRv53olbqGXbfcgF5aiiHmO3xpwEpS5Ld9g==}
'@types/node-fetch@2.6.4':
resolution: {integrity: sha512-1ZX9fcN4Rvkvgv4E6PAY5WXUFWFcRWxZa3EW83UjycOB9ljJCedb2CupIP4RZMEwF/M3eTcCihbBRgwtGbg5Rg==}
'@types/node@20.11.21':
resolution: {integrity: sha512-/ySDLGscFPNasfqStUuWWPfL78jompfIoVzLJPVVAHBh6rpG68+pI2Gk+fNLeI8/f1yPYL4s46EleVIc20F1Ow==}
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node@22.9.0':
resolution: {integrity: sha512-vuyHg81vvWA1Z1ELfvLko2c8f34gyA0zaic0+Rllc5lbCnbSyuvb2Oxpm6TAUAC/2xZN3QGqxBNggD1nNR2AfQ==}
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/opener@1.4.3':
resolution: {integrity: sha512-g7TYSmy2RKZkU3QT/9pMISrhVmQtMNaYq6Aojn3Y6pht29Nu9VuijJCYIjofRj7ZaFtKdxh1I8xf3vdW4l86fg==}
'@types/plist@3.0.5':
resolution: {integrity: sha512-E6OCaRmAe4WDmWNsL/9RMqdkkzDCY1etutkflWk4c+AcjDU07Pcz1fQwTX0TQz+Pxqn9i4L1TU3UFpjnrcDgxA==}
'@types/prop-types@15.7.12':
resolution: {integrity: sha512-5zvhXYtRNRluoE/jAp4GVsSduVUzNWKkOZrCDBWYtE7biZywwdC2AcEzg+cSMLFRfVgeAFqpfNabiPjxFddV1Q==}
'@types/react-dom@18.0.3':
resolution: {integrity: sha512-1RRW9kst+67gveJRYPxGmVy8eVJ05O43hg77G2j5m76/RFJtMbcfAs2viQ2UNsvvDg8F7OfQZx8qQcl6ymygaQ==}
'@types/react-dom@18.3.0':
resolution: {integrity: sha512-EhwApuTmMBmXuFOikhQLIBUn6uFg81SwLMOAUgodJF14SOBOCMdU04gDoYi0WOJJHD144TL32z4yDqCW3dnkQg==}
'@types/react@18.3.3':
resolution: {integrity: sha512-hti/R0pS0q1/xx+TsI73XIqk26eBsISZ2R0wUijXIngRK9R/e7Xw/cXVxQK7R5JjW+SV4zGcn5hXjudkN/pLIw==}
'@types/responselike@1.0.3':
resolution: {integrity: sha512-H/+L+UkTV33uf49PH5pCAUBVPNj2nDBXTN+qS1dOwyyg24l3CcicicCA7ca+HMvJBZcFgl5r8e+RR6elsb4Lyw==}
'@types/scheduler@0.23.0':
resolution: {integrity: sha512-YIoDCTH3Af6XM5VuwGG/QL/CJqga1Zm3NkU3HZ4ZHK2fRMPYP1VczsTUqtsf43PH/iJNVlPHAo2oWX7BSdB2Hw==}
'@types/semver@7.5.8':
resolution: {integrity: sha512-I8EUhyrgfLrcTkzV3TSsGyl1tSuPrEDzr0yd5m90UgNxQkyDXULk3b6MlQqTCpZpNtWe1K0hzclnZkTcLBe2UQ==}
'@types/sharp@0.31.1':
resolution: {integrity: sha512-5nWwamN9ZFHXaYEincMSuza8nNfOof8nmO+mcI+Agx1uMUk4/pQnNIcix+9rLPXzKrm1pS34+6WRDbDV0Jn7ag==}
'@types/shuffle-seed@1.1.3':
resolution: {integrity: sha512-D05NnrEz9YvwCp8GSzyI/UipvOtmiMbEtLgupa5buU6QJkmelKb7Pwuslsb8C7c+Wkn3qiAAL329+/E2PfUd0A==}
'@types/tar@6.1.13':
resolution: {integrity: sha512-IznnlmU5f4WcGTh2ltRu/Ijpmk8wiWXfF0VA4s+HPjHZgvFggk1YaIkbo5krX/zUCzWF8N/l4+W/LNxnvAJ8nw==}
'@types/to-ico@1.1.3':
resolution: {integrity: sha512-3Ew8Hsz/qiDGzwvz75pjRU+6Ocfvrit6hHfirauEdJXxdro73MTe5XdcANh4GZ2wdJqWw9BIuHwWgKAfjUXoGw==}
'@types/tough-cookie@4.0.5':
resolution: {integrity: sha512-/Ad8+nIOV7Rl++6f1BdKxFSMgmoqEoYbHRpPcx3JEfv8VRsQe9Z4mCXeJBzxs7mbHY/XOZZuXlRNfhpVPbs6ZA==}
'@types/validator@13.12.0':
resolution: {integrity: sha512-nH45Lk7oPIJ1RVOF6JgFI6Dy0QpHEzq4QecZhvguxYPDwT8c93prCMqAtiIttm39voZ+DDR+qkNnMpJmMBRqag==}
'@types/verror@1.10.10':
resolution: {integrity: sha512-l4MM0Jppn18hb9xmM6wwD1uTdShpf9Pn80aXTStnK1C94gtPvJcV2FrDmbOQUAQfJ1cKZHktkQUDwEqaAKXMMg==}
'@types/web-bluetooth@0.0.20':
resolution: {integrity: sha512-g9gZnnXVq7gM7v3tJCWV/qw7w+KeOlSHAhgF9RytFyifW6AF61hdT2ucrYhPq9hLs5JIryeupHV3qGk95dH9ow==}
'@types/wicg-file-system-access@2023.10.5':
resolution: {integrity: sha512-e9kZO9kCdLqT2h9Tw38oGv9UNzBBWaR1MzuAavxPcsV/7FJ3tWbU6RI3uB+yKIDPGLkGVbplS52ub0AcRLvrhA==}
'@types/ws@8.5.10':
resolution: {integrity: sha512-vmQSUcfalpIq0R9q7uTo2lXs6eGIpt9wtnLdMv9LVpIjCA/+ufZRozlVoVelIYixx1ugCBKDhn89vnsEGOCx9A==}
'@types/yargs-parser@21.0.3':
resolution: {integrity: sha512-I4q9QU9MQv4oEOz4tAHJtNz1cwuLxn2F3xcc2iV5WdqLPpUnj30aUuxt1mAxYTG+oe8CZMV/+6rU4S4gRDzqtQ==}
'@types/yargs@17.0.32':
resolution: {integrity: sha512-xQ67Yc/laOG5uMfX/093MRlGGCIBzZMarVa+gfNKJxWAIgykYpVGkBdbqEzGDDfCrVUj6Hiff4mTZ5BA6TmAog==}
'@types/yauzl@2.10.3':
resolution: {integrity: sha512-oJoftv0LSuaDZE3Le4DbKX+KS9G36NzOeSap90UIK0yMA/NhKJhqlSGtNDORNRaIbQfzjXDrQa0ytJ6mNRGz/Q==}
'@typescript-eslint/eslint-plugin@8.11.0':
resolution: {integrity: sha512-KhGn2LjW1PJT2A/GfDpiyOfS4a8xHQv2myUagTM5+zsormOmBlYsnQ6pobJ8XxJmh6hnHwa2Mbe3fPrDJoDhbA==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/parser': ^8.0.0 || ^8.0.0-alpha.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint: ^8.57.0 || ^9.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
typescript:
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/parser@8.11.0':
resolution: {integrity: sha512-lmt73NeHdy1Q/2ul295Qy3uninSqi6wQI18XwSpm8w0ZbQXUpjCAWP1Vlv/obudoBiIjJVjlztjQ+d/Md98Yxg==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint: ^8.57.0 || ^9.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
typescript:
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/scope-manager@8.11.0':
resolution: {integrity: sha512-Uholz7tWhXmA4r6epo+vaeV7yjdKy5QFCERMjs1kMVsLRKIrSdM6o21W2He9ftp5PP6aWOVpD5zvrvuHZC0bMQ==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@typescript-eslint/type-utils@8.11.0':
resolution: {integrity: sha512-ItiMfJS6pQU0NIKAaybBKkuVzo6IdnAhPFZA/2Mba/uBjuPQPet/8+zh5GtLHwmuFRShZx+8lhIs7/QeDHflOg==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
typescript:
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/types@8.11.0':
resolution: {integrity: sha512-tn6sNMHf6EBAYMvmPUaKaVeYvhUsrE6x+bXQTxjQRp360h1giATU0WvgeEys1spbvb5R+VpNOZ+XJmjD8wOUHw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@typescript-eslint/typescript-estree@8.11.0':
resolution: {integrity: sha512-yHC3s1z1RCHoCz5t06gf7jH24rr3vns08XXhfEqzYpd6Hll3z/3g23JRi0jM8A47UFKNc3u/y5KIMx8Ynbjohg==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
typescript:
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/utils@8.11.0':
resolution: {integrity: sha512-CYiX6WZcbXNJV7UNB4PLDIBtSdRmRI/nb0FMyqHPTQD1rMjA0foPLaPUV39C/MxkTd/QKSeX+Gb34PPsDVC35g==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint: ^8.57.0 || ^9.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/visitor-keys@8.11.0':
resolution: {integrity: sha512-EaewX6lxSjRJnc+99+dqzTeoDZUfyrA52d2/HRrkI830kgovWsmIiTfmr0NZorzqic7ga+1bS60lRBUgR3n/Bw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
'@vitejs/plugin-react@4.3.3':
resolution: {integrity: sha512-NooDe9GpHGqNns1i8XDERg0Vsg5SSYRhRxxyTGogUdkdNt47jal+fbuYi+Yfq6pzRCKXyoPcWisfxE6RIM3GKA==}
engines: {node: ^14.18.0 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vite: ^4.2.0 || ^5.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitejs/plugin-vue@5.0.5':
resolution: {integrity: sha512-LOjm7XeIimLBZyzinBQ6OSm3UBCNVCpLkxGC0oWmm2YPzVZoxMsdvNVimLTBzpAnR9hl/yn1SHGuRfe6/Td9rQ==}
engines: {node: ^18.0.0 || >=20.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vite: ^5.0.0
vue: ^3.2.25
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/coverage-v8@1.6.0':
resolution: {integrity: sha512-KvapcbMY/8GYIG0rlwwOKCVNRc0OL20rrhFkg/CHNzncV03TE2XWvO5w9uZYoxNiMEBacAJt3unSOiZ7svePew==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vitest: 1.6.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/expect@1.6.0':
resolution: {integrity: sha512-ixEvFVQjycy/oNgHjqsL6AZCDduC+tflRluaHIzKIsdbzkLn2U/iBnVeJwB6HsIjQBdfMR8Z0tRxKUsvFJEeWQ==}
'@vitest/runner@1.6.0':
resolution: {integrity: sha512-P4xgwPjwesuBiHisAVz/LSSZtDjOTPYZVmNAnpHHSR6ONrf8eCJOFRvUwdHn30F5M1fxhqtl7QZQUk2dprIXAg==}
'@vitest/snapshot@1.6.0':
resolution: {integrity: sha512-+Hx43f8Chus+DCmygqqfetcAZrDJwvTj0ymqjQq4CvmpKFSTVteEOBzCusu1x2tt4OJcvBflyHUE0DZSLgEMtQ==}
'@vitest/spy@1.6.0':
resolution: {integrity: sha512-leUTap6B/cqi/bQkXUu6bQV5TZPx7pmMBKBQiI0rJA8c3pB56ZsaTbREnF7CJfmvAS4V2cXIBAh/3rVwrrCYgw==}
'@vitest/utils@1.6.0':
resolution: {integrity: sha512-21cPiuGMoMZwiOHa2i4LXkMkMkCGzA+MVFV70jRwHo95dL4x/ts5GZhML1QWuy7yfp3WzK3lRvZi3JnXTYqrBw==}
'@volar/language-core@2.4.0-alpha.12':
resolution: {integrity: sha512-Dj9qTifcGGgzFLfMbU5dCo13kHyNuEyvPJhtWDnoVBBmgwW3GMwFmgWnNxBhjf63m5x0gux1okaxX2CLN7qSww==}
'@volar/source-map@2.4.0-alpha.12':
resolution: {integrity: sha512-LXATFSj4D7T9sEm7FFj6iBgHjKjrdhAgRPcechVKiNCMQdr3r3GVkkeu8aM+1peaMH3LsCqoDxVZEmh2r7CHiw==}
'@volar/typescript@2.4.0-alpha.12':
resolution: {integrity: sha512-mLg+OQauMTv/+08a7WBWJo1sev/wc8t2is0zhBZIlFU+j5mG89FM4+4089c2p/zoUFZ400Q/VNg2BPfhpZ8wSA==}
'@vue/babel-helper-vue-transform-on@1.2.2':
resolution: {integrity: sha512-nOttamHUR3YzdEqdM/XXDyCSdxMA9VizUKoroLX6yTyRtggzQMHXcmwh8a7ZErcJttIBIc9s68a1B8GZ+Dmvsw==}
'@vue/babel-plugin-jsx@1.2.2':
resolution: {integrity: sha512-nYTkZUVTu4nhP199UoORePsql0l+wj7v/oyQjtThUVhJl1U+6qHuoVhIvR3bf7eVKjbCK+Cs2AWd7mi9Mpz9rA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/babel-plugin-resolve-type@1.2.2':
resolution: {integrity: sha512-EntyroPwNg5IPVdUJupqs0CFzuf6lUrVvCspmv2J1FITLeGnUCuoGNNk78dgCusxEiYj6RMkTJflGSxk5aIC4A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': ^7.0.0-0
'@vue/compiler-core@3.5.2':
resolution: {integrity: sha512-1aP7FL2GkqfcskHWGg3lfWQpJnrmewKc+rNJ/hq9WNaAw4BEyJ5QbNChnqmbw+tJ409zdy1XWmUeXXMrCKJcQQ==}
'@vue/compiler-dom@3.5.2':
resolution: {integrity: sha512-QY4DpT8ZIUyu/ZA5gErpSEDocGNEbHmpkZIC/d5jbp/rUF0iOJNigAy3HCCKc0PMMhDlrcysO3ufQ6Ab4MpEcQ==}
'@vue/compiler-sfc@3.5.2':
resolution: {integrity: sha512-vErEtybSU290LbMW+ChYllI9tNJEdTW1oU+8cZWINZyjlWeTSa9YqDl4/pZJSnozOI+HmcaC1Vz2eFKmXNSXZA==}
'@vue/compiler-ssr@3.5.2':
resolution: {integrity: sha512-vMtA4tQK/AM3UAYJsmouQzQpgG+h9TKiD5BV+Zt+ZyAMdicxzSEEFGWf/CykRnDpqj9fMfIHPhOezJVNxiXe2A==}
'@vue/devtools-api@6.6.3':
resolution: {integrity: sha512-0MiMsFma/HqA6g3KLKn+AGpL1kgKhFWszC9U29NfpWK5LE7bjeXxySWJrOJ77hBz+TBrBQ7o4QJqbPbqbs8rJw==}
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-core@7.6.3':
resolution: {integrity: sha512-C7FOuh3Z+EmXXzDU9eRjHQL7zW7/CFovM6yCNNpUb+zXxhrn4fiqTum+a3gNau9DuzYfEtQXwZ9F7MeK0JKYVw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vue: ^3.0.0
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-kit@7.6.3':
resolution: {integrity: sha512-ETsFc8GlOp04rSFN79tB2TpVloWfsSx9BoCSElV3w3CaJTSBfz42KsIi5Ka+dNTJs1jY7QVLTDeoBmUGgA9h2A==}
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-shared@7.6.3':
resolution: {integrity: sha512-wJW5QF27i16+sNQIaes8QoEZg1eqEgF83GkiPUlEQe9k7ZoHXHV7PRrnrxOKem42sIHPU813J2V/ZK1uqTJe6g==}
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/eslint-config-typescript@14.1.3':
resolution: {integrity: sha512-L4NUJQz/0We2QYtrNwRAGRy4KfpOagl5V3MpZZ+rQ51a+bKjlKYYrugi7lp7PIX8LolRgu06ZwDoswnSGWnAmA==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint: ^9.10.0
eslint-plugin-vue: ^9.28.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '>=4.8.4'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
typescript:
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/language-core@2.0.24':
resolution: {integrity: sha512-997YD6Lq/66LXr3ZOLNxDCmyn13z9NP8LU1UZn9hGCDWhzlbXAIP0hOgL3w3x4RKEaWTaaRtsHP9DzHvmduruQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
typescript:
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/reactivity@3.5.2':
resolution: {integrity: sha512-lJwWL5bNht+2vIwU/+lnGdH+FKFxzz6z8WkoIJityPLiasWU+HDUvEsC7gm3JFwbTf7Kk+Nr9kJMaPy0HXwwxQ==}
'@vue/runtime-core@3.5.2':
resolution: {integrity: sha512-oU+i9sJjGEMfEhlrJ7SZv7CdSIgUNyBHnWHa0SqU2RF48V3/ATajzpWq1/DkiVJ1mtx+cQFAMKs8s/3cB3YlLQ==}
'@vue/runtime-dom@3.5.2':
resolution: {integrity: sha512-2qvysn+oR0QnFKaWZxQ90iVpWAK/WPpYmODHCv24IDXjsBrdHbjLBj9s6YBdPaMuQhs0LNsmhsgZYZBkszLg6g==}
'@vue/server-renderer@3.5.2':
resolution: {integrity: sha512-3POhYCA8KfbmuDuUiNbMXnpdh9pwE4SvAqo7VvACjklLkf3AaMkY3TvV7APeEa/WQezrnL+E4X2ASpJsKeS4cQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/shared@3.5.2':
resolution: {integrity: sha512-Ce89WNFBzcDca/AgFTxgX4/K4iAyF7oFIp8Z5aBbFBNbtpwnQr+5pZOoHndxnjE2h+YFcipVMzs9UL11XB6dwA==}
'@vue/test-utils@2.4.6':
resolution: {integrity: sha512-FMxEjOpYNYiFe0GkaHsnJPXFHxQ6m4t8vI/ElPGpMWxZKpmRvQ33OIrvRXemy6yha03RxhOlQuy+gZMC3CQSow==}
'@vue/tsconfig@0.5.1':
resolution: {integrity: sha512-VcZK7MvpjuTPx2w6blwnwZAu5/LgBUtejFOi3pPGQFXQN5Ela03FUtd2Qtg4yWGGissVL0dr6Ro1LfOFh+PCuQ==}
'@vueuse/core@10.11.0':
resolution: {integrity: sha512-x3sD4Mkm7PJ+pcq3HX8PLPBadXCAlSDR/waK87dz0gQE+qJnaaFhc/dZVfJz+IUYzTMVGum2QlR7ImiJQN4s6g==}
'@vueuse/gesture@2.0.0':
resolution: {integrity: sha512-+F0bhhd8j+gxHaXG4fJgfokrkFfWenQ10MtrWOJk68B5UaTwtJm4EpsZFiVdluA3jpKExG6H+HtroJpvO7Qx0A==}
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/composition-api': ^1.4.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
vue: ^2.0.0 || >=3.0.0-rc.0
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/composition-api':
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vueuse/metadata@10.11.0':
resolution: {integrity: sha512-kQX7l6l8dVWNqlqyN3ePW3KmjCQO3ZMgXuBMddIu83CmucrsBfXlH+JoviYyRBws/yLTQO8g3Pbw+bdIoVm4oQ==}
'@vueuse/shared@10.11.0':
resolution: {integrity: sha512-fyNoIXEq3PfX1L3NkNhtVQUSRtqYwJtJg+Bp9rIzculIZWHTkKSysujrOk2J+NrRulLTQH9+3gGSfYLWSEWU1A==}
'@xmldom/xmldom@0.8.10':
resolution: {integrity: sha512-2WALfTl4xo2SkGCYRt6rDTFfk9R1czmBvUQy12gK2KuRKIpWEhcbbzy8EZXtz/jkRqHX8bFEc6FC1HjX4TUWYw==}
engines: {node: '>=10.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
abbrev@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6/mh1E2u2YgEsCHdY0Yx5oW+61gZU+1vXaoiHHrpKeuRNNgFvS+/jrwHiQhB5apAf5oB7UB7E19ol2R2LKH8hQ==}
engines: {node: ^14.17.0 || ^16.13.0 || >=18.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
abstract-leveldown@6.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BsLm5vFMRUrrLeCcRc+G0t2qOaTzpoJQLOubq2XM72eNpjF5UdU5o/5NvlNhx95XHcAvcl8OMXr4mlg/fRgUXQ==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
abstract-leveldown@6.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TU5nlYgta8YrBMNpc9FwQzRbiXsj49gsALsXadbGHt9CROPzX5fB0rWDR5mtdpOOKa5XqRFpbj1QroPAoPzVjQ==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
acorn-jsx@5.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rq9s+JNhf0IChjtDXxllJ7g41oZk5SlXtp0LHwyA5cejwn7vKmKp4pPri6YEePv2PU65sAsegbXtIinmDFDXgQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
acorn: ^6.0.0 || ^7.0.0 || ^8.0.0
acorn-walk@8.3.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MxXdReSRhGO7VlFe1bRG/oI7/mdLV9B9JJT0N8vZOhF7gFRR5l3M8W9G8JxmKV+JC5mGqJ0QvqfSOLsCPa4nUw==}
engines: {node: '>=0.4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
acorn@8.12.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RTvkC4w+KNXrM39/lWCUaG0IbRkWdCv7W/IOW9oU6SawyxulvkQy5HQPVTKxEjczcUvapcrw3cFx/60VN/NRNw==}
engines: {node: '>=0.4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-charts-community@9.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jw2llxTYzGAZ24m7eQsKS24BnJBhspZKsL03DbqH0wxLepbEcC3eeWICe+02TBQCbFVsWmSsYukjzQg3FkVWRw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-grid-community@31.3.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jOxQO86C6eLnk1GdP24HB6aqaouFzMWizgfUwNY5MnetiWzz9ZaAmOGSnW/XBvdjXvC5Fpk3gSbvVKKQ7h9kBw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-grid-enterprise@31.3.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kreGRsFjz41APXXchLcQFtginnrmIGQYH48p7ydz33x8v+aja06HS5yEM6NP8j+VVHX43LeXnsl5Y4TLRgSoeg==}
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-grid-vue3@31.3.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MFsWKeWBuzexc3hkOtDsZw4xkXfVT6B267DcUmZGy92otgGfd/I8qMKhGr1qnUnel9Jy5OKeBS+jQusfmO2/SA==}
Table Editor Widget (#10774) Fixes #10293 The Table Editor Widget allows adding rows and columns, editing cells and renaming columns. [Screencast from 2024-08-07 13-17-37.webm](https://github.com/user-attachments/assets/d2e708b5-6516-4107-bc17-f018e455c111) # Important Notes * The parts of Table Visualization which were useful for the widget were put in vue component. On this occasion, we use aggrid vue.
2024-08-12 17:45:58 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
agent-base@6.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RZNwNclF7+MS/8bDg70amg32dyeZGZxiDuQmZxKLAlQjr3jGyLx+4Kkk58UO7D2QdgFIQCovuSuZESne6RG6XQ==}
engines: {node: '>= 6.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
agent-base@7.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-H0TSyFNDMomMNJQBn8wFV5YC/2eJ+VXECwOadZJT554xP6cODZHPX3H9QMQECxvrgiSOP1pHjy1sMWQVYJOUOA==}
engines: {node: '>= 14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ajv-keywords@3.5.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5p6WTN0DdTGVQk6VjcEju19IgaHudalcfabD7yhDGeA6bcQnmL+CpveLJq/3hvfwd1aof6L386Ougkx6RfyMIQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
ajv: ^6.9.1
ajv@6.12.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-j3fVLgvTo527anyYyJOGTYJbG+vnnQYvE0m5mmkc1TK+nxAppkCLMIL0aZ4dblVCNoGShhm+kzE4ZUykBoMg4g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ajv@8.16.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-F0twR8U1ZU67JIEtekUcLkXkoO5mMMmgGD8sK/xUFzJ805jxHQl92hImFAqqXMyMYjSPOyUPAwHYhB72g5sTXw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
amazon-cognito-identity-js@6.3.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kBq+GE6OkLrxtFj3ZduIOlKBFYeOqZK3EhxbDBkv476UTvy+uwfR0tlriTq2QzNdnvlQAjBIXnXuOM7DwR1UEQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ansi-regex@5.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-quJQXlTSUGL2LH9SUXo8VwsY4soanhgo6LNSm84E1LBcE8s3O0wpdiRzyR9z/ZZJMlMWv37qOOb9pdJlMUEKFQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ansi-regex@6.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-n5M855fKb2SsfMIiFFoVrABHJC8QtHwVx+mHWP3QcEqBHYienj5dHSgjbxtC0WEZXYt4wcD6zrQElDPhFuZgfA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ansi-styles@3.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VT0ZI6kZRdTh8YyJw3SMbYm/u+NqfsAxEpWO0Pf9sq8/e94WxxOpPKx9FR1FlyCtOVDNOQ+8ntlqFxiRc+r5qA==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ansi-styles@4.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zbB9rCJAT1rbjiVDb2hqKFHNYLxgtk8NURxZ3IZwD3F6NtxbXZQCnnSi1Lkx+IDohdPlFp222wVALIheZJQSEg==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ansi-styles@5.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Cxwpt2SfTzTtXcfOlzGEee8O+c+MmUgGrNiBcXnuWxuFJHe6a5Hz7qwhwe5OgaSYI0IJvkLqWX1ASG+cJOkEiA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ansi-styles@6.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bN798gFfQX+viw3R7yrGWRqnrN2oRkEkUjjl4JNn4E8GxxbjtG3FbrEIIY3l8/hrwUwIeCZvi4QuOTP4MErVug==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
any-promise@1.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7UvmKalWRt1wgjL1RrGxoSJW/0QZFIegpeGvZG9kjp8vrRu55XTHbwnqq2GpXm9uLbcuhxm3IqX9OB4MZR1b2A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
anymatch@3.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KMReFUr0B4t+D+OBkjR3KYqvocp2XaSzO55UcB6mgQMd3KbcE+mWTyvVV7D/zsdEbNnV6acZUutkiHQXvTr1Rw==}
engines: {node: '>= 8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
app-builder-bin@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xwdG0FJPQMe0M0UA4Tz0zEB8rBJTRA5a476ZawAqiBkMv16GRK5xpXThOjMaEOFnZ6zabejjG4J3da0SXG63KA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
app-builder-lib@24.13.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FAzX6IBit2POXYGnTCT8YHFO/lr5AapAII6zzhQO3Rw4cEDOgK+t1xhLc5tNcKlicTHlo9zxIwnYCX9X2DLkig==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
dmg-builder: 24.13.3
electron-builder-squirrel-windows: 24.13.3
archiver-utils@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bEL/yUb/fNNiNTuUz979Z0Yg5L+LzLxGJz8x79lYmR54fmTIb6ob/hNQgkQnIUDWIFjZVQwl9Xs356I6BAMHfw==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
archiver-utils@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KVgf4XQVrTjhyWmx6cte4RxonPLR9onExufI1jhvw/MQ4BB6IsZD5gT8Lq+u/+pRkWna/6JoHpiQioaqFP5Rzw==}
engines: {node: '>= 10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
archiver@5.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+25nxyyznAXF7Nef3y0EbBeqmGZgeN/BxHX29Rs39djAfaFalmQ89SE6CWyDCHzGL0yt/ycBtNOmGTW0FyGWNw==}
engines: {node: '>= 10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
are-docs-informative@0.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ixiS0nLNNG5jNQzgZJNoUpBKdo9yTYZMGJ+QgT2jmjR7G7+QHRCc4v6LQ3NgE7EBJq+o0ams3waJwkrlBom8Ig==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
arg@5.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PYjyFOLKQ9y57JvQ6QLo8dAgNqswh8M1RMJYdQduT6xbWSgK36P/Z/v+p888pM69jMMfS8Xd8F6I1kQ/I9HUGg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
argparse@1.0.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-o5Roy6tNG4SL/FOkCAN6RzjiakZS25RLYFrcMttJqbdd8BWrnA+fGz57iN5Pb06pvBGvl5gQ0B48dJlslXvoTg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
argparse@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8+9WqebbFzpX9OR+Wa6O29asIogeRMzcGtAINdpMHHyAg10f05aSFVBbcEqGf/PXw1EjAZ+q2/bEBg3DvurK3Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
array-buffer-byte-length@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ahC5W1xgou+KTXix4sAO8Ki12Q+jf4i0+tmk3sC+zgcynshkHxzpXdImBehiUYKKKDwvfFiJl1tZt6ewscS1Mg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
array-includes@3.1.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-itaWrbYbqpGXkGhZPGUulwnhVf5Hpy1xiCFsGqyIGglbBxmG5vSjxQen3/WGOjPpNEv1RtBLKxbmVXm8HpJStQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
array.prototype.findlast@1.2.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CVvd6FHg1Z3POpBLxO6E6zr+rSKEQ9L6rZHAaY7lLfhKsWYUBBOuMs0e9o24oopj6H+geRCX0YJ+TJLBK2eHyQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
array.prototype.flat@1.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-djYB+Zx2vLewY8RWlNCUdHjDXs2XOgm602S9E7P/UpHgfeHL00cRiIF+IN/G/aUJ7kGPb6yO/ErDI5V2s8iycA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
array.prototype.flatmap@1.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Ewyx0c9PmpcsByhSW4r+9zDU7sGjFc86qf/kKtuSCRdhfbk0SNLLkaT5qvcHnRGgc5NP/ly/y+qkXkqONX54CQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
array.prototype.tosorted@1.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-p6Fx8B7b7ZhL/gmUsAy0D15WhvDccw3mnGNbZpi3pmeJdxtWsj2jEaI4Y6oo3XiHfzuSgPwKc04MYt6KgvC/wA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
arraybuffer.prototype.slice@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bMxMKAjg13EBSVscxTaYA4mRc5t1UAXa2kXiGTNfZ079HIWXEkKmkgFrh/nJqamaLSrXO5H4WFFkPEaLJWbs3A==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
arrify@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3CYzex9M9FGQjCGMGyi6/31c8GJbgb0qGyrx5HWxPd0aCwh4cB2YjMb2Xf9UuoogrMrlO9cTqnB5rI5GHZTcUA==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
asn1@0.2.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ix/FxPn0MDjeyJ7i/yoHGFt/EX6LyNbxSEhPPXODPL+KB0VPk86UYfL0lMdy+KCnv+fmvIzySwaK5COwqVbWTQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
assert-plus@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NfJ4UzBCcQGLDlQq7nHxH+tv3kyZ0hHQqF5BO6J7tNJeP5do1llPr8dZ8zHonfhAu0PHAdMkSo+8o0wxg9lZWw==}
engines: {node: '>=0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
assertion-error@1.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jgsaNduz+ndvGyFt3uSuWqvy4lCnIJiovtouQN5JZHOKCS2QuhEdbcQHFhVksz2N2U9hXJo8odG7ETyWlEeuDw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
astral-regex@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Z7tMw1ytTXt5jqMcOP+OQteU1VuNK9Y02uuJtKQ1Sv69jXQKKg5cibLwGJow8yzZP+eAc18EmLGPal0bp36rvQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
async-exit-hook@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NW2cX8m1Q7KPA7a5M2ULQeZ2wR5qI5PAbw5L0UOMxdioVk9PMZ0h1TmyZEkPYrCvYjDlFICusOu1dlEKAAeXBw==}
engines: {node: '>=0.12.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
async@2.6.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mzo5dfJYwAn29PeiJ0zvwTo04zj8HDJj0Mn8TD7sno7q12prdbnasKJHhkm2c1LgrhlJ0teaea8860oxi51mGA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
async@3.2.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-htCUDlxyyCLMgaM3xXg0C0LW2xqfuQ6p05pCEIsXuyQ+a1koYKTuBMzRNwmybfLgvJDMd0r1LTn4+E0Ti6C2AA==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
asynckit@0.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Oei9OH4tRh0YqU3GxhX79dM/mwVgvbZJaSNaRk+bshkj0S5cfHcgYakreBjrHwatXKbz+IoIdYLxrKim2MjW0Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
at-least-node@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+q/t7Ekv1EDY2l6Gda6LLiX14rU9TV20Wa3ofeQmwPFZbOMo9DXrLbOjFaaclkXKWidIaopwAObQDqwWtGUjqg==}
engines: {node: '>= 4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
available-typed-arrays@1.0.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wvUjBtSGN7+7SjNpq/9M2Tg350UZD3q62IFZLbRAR1bSMlCo1ZaeW+BJ+D090e4hIIZLBcTDWe4Mh4jvUDajzQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
aws-sign2@0.7.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-08kcGqnYf/YmjoRhfxyu+CLxBjUtHLXLXX/vUfx9l2LYzG3c1m61nrpyFUZI6zeS+Li/wWMMidD9KgrqtGq3mA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
aws4@1.13.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3AungXC4I8kKsS9PuS4JH2nc+0bVY/mjgrephHTIi8fpEeGsTHBUJeosp0Wc1myYMElmD0B3Oc4XL/HVJ4PV2g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
babel-plugin-react-compiler@19.0.0-beta-6fc168f-20241025:
resolution: {integrity: sha512-wFVeXhF0hkiRe4bEM0jzeTFMlMbcKNTwhXcFvqUIVB6WXf+3vdwOWGWnw7jwvDb2mzvsIZOFt/96itOFt1rwjw==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
balanced-match@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3oSeUO0TMV67hN1AmbXsK4yaqU7tjiHlbxRDZOpH0KW9+CeX4bRAaX0Anxt0tx2MrpRpWwQaPwIlISEJhYU5Pw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
base64-js@1.5.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AKpaYlHn8t4SVbOHCy+b5+KKgvR4vrsD8vbvrbiQJps7fKDTkjkDry6ji0rUJjC0kzbNePLwzxq8iypo41qeWA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bcrypt-pbkdf@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qeFIXtP4MSoi6NLqO12WfqARWWuCKi2Rn/9hJLEmtB5yTNr9DqFWkJRCf2qShWzPeAMRnOgCrq0sg/KLv5ES9w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bignumber.js@2.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-uw4ra6Cv483Op/ebM0GBKKfxZlSmn6NgFRby5L3yGTlunLj53KQgndDlqy2WVFOwgvurocApYkSud0aO+mvrpQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
binary-extensions@2.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Ceh+7ox5qe7LJuLHoY0feh3pHuUDHAcRUeyL2VYghZwfpkNIy/+8Ocg0a3UuSoYzavmylwuLWQOf3hl0jjMMIw==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
birpc@0.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-B64AGL4ug2IS2jvV/zjTYDD1L+2gOJTT7Rv+VaK7KVQtQOo/xZbCDsh7g727ipckmU+QJYRqo5RcifVr0Kgcmg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
birpc@0.2.19:
resolution: {integrity: sha512-5WeXXAvTmitV1RqJFppT5QtUiz2p1mRSYU000Jkft5ZUCLJIk4uQriYNO50HknxKwM6jd8utNc66K1qGIwwWBQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bl@4.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1W07cM9gS6DcLperZfFSj+bWLtaPGSOHWhPiGzXmvVJbRLdG82sH/Kn8EtW1VqWVA54AKf2h5k5BbnIbwF3h6w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bluebird-lst@1.0.9:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7B1Rtx82hjnSD4PGLAjVWeYH3tHAcVUmChh85a3lltKQm6FresXh9ErQo6oAv6CqxttczC3/kEg8SY5NluPuUw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bluebird@3.7.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XpNj6GDQzdfW+r2Wnn7xiSAd7TM3jzkxGXBGTtWKuSXv1xUV+azxAm8jdWZN06QTQk+2N2XB9jRDkvbmQmcRtg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bmp-js@0.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-OS74Rlt0Aynu2mTPmY9RZOUOXlqWecFIILFXr70vv16/xCZnFxvri9IKkF1IGxQ8r9dOE62qGNpKxXx8Lko8bg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bmp-js@0.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-epsm3Z92j5xwek9p97pVw3KbsNc0F4QnbYh+N93SpbJYuHFQQ/UAh6K+bKFGyLePH3Hudtl/Sa95Quqp0gX8IQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
body-parser@1.20.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ml9pReCu3M61kGlqoTm2umSXTlRTuGTx0bfYj+uIUKKYycG5NtSbeetV3faSU6R7ajOPw0g/J1PvK4qNy7s5bA==}
engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
boolbase@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JZOSA7Mo9sNGB8+UjSgzdLtokWAky1zbztM3WRLCbZ70/3cTANmQmOdR7y2g+J0e2WXywy1yS468tY+IruqEww==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
boolean@3.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-d0II/GO9uf9lfUHH2BQsjxzRJZBdsjgsBiW4BvhWk/3qoKwQFjIDVN19PfX8F2D/r9PCMTtLWjYVCFrpeYUzsw==}
Metadata should not depend on absolute text spans (#11390) close #11304 Changelog: - update: add `ide.snapshot` optional metadata field containing the source code of the file - update: `syncFileContents` method tries to repair the metadata spans when it detects that the source file was edited and the received code does not match the code stored in the `ide.snapshot` metadata field # Important Notes Tested in gui
2024-10-28 12:41:46 +03:00
deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bowser@2.11.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AlcaJBi/pqqJBIQ8U9Mcpc9i8Aqxn88Skv5d+xBX006BY5u8N3mGLHa5Lgppa7L/HfwgwLgZ6NYs+Ag6uUmJRA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
brace-expansion@1.1.11:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iCuPHDFgrHX7H2vEI/5xpz07zSHB00TpugqhmYtVmMO6518mCuRMoOYFldEBl0g187ufozdaHgWKcYFb61qGiA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
brace-expansion@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XnAIvQ8eM+kC6aULx6wuQiwVsnzsi9d3WxzV3FpWTGA19F621kwdbsAcFKXgKUHZWsy+mY6iL1sHTxWEFCytDA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
braces@3.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-b8um+L1RzM3WDSzvhm6gIz1yfTbBt6YTlcEKAvsmqCZZFw46z626lVj9j1yEPW33H5H+lBQpZMP1k8l+78Ha0A==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
browserslist@4.23.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-btwCFJVjI4YWDNfau8RhZ+B1Q/VLoUITrm3RlP6y1tYGWIOa+InuYiRGXUBXo8nA1qKmHMyLB/iVQg5TT4eFoA==}
engines: {node: ^6 || ^7 || ^8 || ^9 || ^10 || ^11 || ^12 || >=13.7}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
hasBin: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-alloc-unsafe@1.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TEM2iMIEQdJ2yjPJoSIsldnleVaAk1oW3DBVUykyOLsEsFmEc9kn+SFFPz+gl54KQNxlDnAwCXosOS9Okx2xAg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-alloc@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CFsHQgjtW1UChdXgbyJGtnm+O/uLQeZdtbDo8mfUgYXCHSM1wgrVxXm6bSyrUuErEb+4sYVGCzASBRot7zyrow==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-crc32@0.2.13:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VO9Ht/+p3SN7SKWqcrgEzjGbRSJYTx+Q1pTQC0wrWqHx0vpJraQ6GtHx8tvcg1rlK1byhU5gccxgOgj7B0TDkQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-equal@0.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RgSV6InVQ9ODPdLWJ5UAqBqJBOg370Nz6ZQtRzpt6nUjc8v0St97uJ4PYC6NztqIScrAXafKM3mZPMygSe1ggA==}
engines: {node: '>=0.4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-equal@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QoV3ptgEaQpvVwbXdSO39iqPQTCxSF7A5U99AxbHYqUdCizL/lH2Z0A2y6nbZucxMEOtNyZfG2s6gsVugGpKkg==}
engines: {node: '>=0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-fill@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-T7zexNBwiiaCOGDg9xNX9PBmjrubblRkENuptryuI64URkXDFum9il/JGL8Lm8wYfAXpredVXXZz7eMHilimiQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-from@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-E+XQCRwSbaaiChtv6k6Dwgc+bx+Bs6vuKJHHl5kox/BaKbhiXzqQOwK4cO22yElGp2OCmjwVhT3HmxgyPGnJfQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer@4.9.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xq+q3SRMOxGivLhBNaUdC64hDTQwejJ+H0T/NB1XMtTVEwNTrfFF3gAxiyW0Bu/xWEGhjVKgUcMhCrUy2+uCWg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer@5.7.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EHcyIPBQ4BSGlvjB16k5KgAJ27CIsHY/2JBmCRReo48y9rQ3MaUzWX3KVlBa4U7MyX02HdVj0K7C3WaB3ju7FQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
builder-util-runtime@9.2.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-upp+biKpN/XZMLim7aguUyW8s0FUpDvOtK6sbanMFDAMBzpHDqdhgVYm6zc9HJ6nWo7u2Lxk60i2M6Jd3aiNrA==}
engines: {node: '>=12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
builder-util@24.13.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NhbCSIntruNDTOVI9fdXz0dihaqX2YuE1D6zZMrwiErzH4ELZHE6mdiB40wEgZNprDia+FghRFgKoAqMZRRjSA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bundle-name@4.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tjwM5exMg6BGRI+kNmTntNsvdZS1X8BFYS6tnJ2hdH0kVxM6/eVZ2xy+FqStSWvYmtfFMDLIxurorHwDKfDz5Q==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bytes@3.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/Nf7TyzTx6S3yRJObOAV7956r8cr2+Oj8AC5dt8wSP3BQAoeX58NoHyCU8P8zGkNXStjTSi6fzO6F0pBdcYbEg==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cac@6.7.14:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-b6Ilus+c3RrdDk+JhLKUAQfzzgLEPy6wcXqS7f/xe1EETvsDP6GORG7SFuOs6cID5YkqchW/LXZbX5bc8j7ZcQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cacheable-lookup@5.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2/kNscPhpcxrOigMZzbiWF7dz8ilhb/nIHU3EyZiXWXpeq/au8qJ8VhdftMkty3n7Gj6HIGalQG8oiBNB3AJgA==}
engines: {node: '>=10.6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cacheable-request@7.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-v+p6ongsrp0yTGbJXjgxPow2+DL93DASP4kXCDKb8/bwRtt9OEF3whggkkDkGNzgcWy2XaF4a8nZglC7uElscg==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
call-bind@1.0.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GHTSNSYICQ7scH7sZ+M2rFopRoLh8t2bLSW6BbgrtLsahOIB5iyAVJf9GjWK3cYTDaMj4XdBpM1cA6pIS0Kv2w==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
call-me-maybe@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HpX65o1Hnr9HH25ojC1YGs7HCQLq0GCOibSaWER0eNpgJ/Z1MZv2mTc7+xh6WOPxbRVcmgbv4hGU+uSQ/2xFZQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
callsites@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-P8BjAsXvZS+VIDUI11hHCQEv74YT67YUi5JJFNWIqL235sBmjX4+qx9Muvls5ivyNENctx46xQLQ3aTuE7ssaQ==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
camel-case@4.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gxGWBrTT1JuMx6R+o5PTXMmUnhnVzLQ9SNutD4YqKtI6ap897t3tKECYla6gCWEkplXnlNybEkZg9GEGxKFCgw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
camelcase-css@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QOSvevhslijgYwRx6Rv7zKdMF8lbRmx+uQGx2+vDc+KI/eBnsy9kit5aj23AgGu3pa4t9AgwbnXWqS+iOY+2aA==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
camelcase@6.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Gmy6FhYlCY7uOElZUSbxo2UCDH8owEk996gkbrpsgGtrJLM3J7jGxl9Ic7Qwwj4ivOE5AWZWRMecDdF7hqGjFA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
caniuse-lite@1.0.30001658:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-N2YVqWbJELVdrnsW5p+apoQyYt51aBMSsBZki1XZEfeBCexcM/sf4xiAHcXQBkuOwJBXtWF7aW1sYX6tKebPHw==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
capital-case@1.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ds37W8CytHgwnhGGTi88pcPyR15qoNkOpYwmMMfnWqqWgESapLqvDx6huFjQ5vqWSn2Z06173XNA7LtMOeUh1A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
caseless@0.12.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4tYFyifaFfGacoiObjJegolkwSU4xQNGbVgUiNYVUxbQ2x2lUsFvY4hVgVzGiIe6WLOPqycWXA40l+PWsxthUw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chai@4.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-13sOfMv2+DWduEU+/xbun3LScLoqN17nBeTLUsmDfKdoiC1fr0n9PU4guu4AhRcOVFk/sW8LyZWHuhWtQZiF+g==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chalk@2.4.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Mti+f9lpJNcwF4tWV8/OrTTtF1gZi+f8FqlyAdouralcFWFQWF2+NgCHShjkCb+IFBLq9buZwE1xckQU4peSuQ==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chalk@4.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oKnbhFyRIXpUuez8iBMmyEa4nbj4IOQyuhc/wy9kY7/WVPcwIO9VA668Pu8RkO7+0G76SLROeyw9CpQ061i4mA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chalk@5.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dLitG79d+GV1Nb/VYcCDFivJeK1hiukt9QjRNVOsUtTy1rR1YJsmpGGTZ3qJos+uw7WmWF4wUwBd9jxjocFC2w==}
engines: {node: ^12.17.0 || ^14.13 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
change-case@4.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bSxY2ws9OtviILG1EiY5K7NNxkqg/JnRnFxLtKQ96JaviiIxi7djMrSd0ECT9AC+lttClmYwKw53BWpOMblo7A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
char-regex@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oSvEeo6ZUD7NepqAat3RqoucZ5SeqLJgOvVIwkafu6IP3V0pO38s/ypdVUmDDK6qIIHNlYHJAKX9E7R7HoKElw==}
engines: {node: '>=12.20'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
check-error@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iKEoDYaRmd1mxM90a2OEfWhjsjPpYPuQ+lMYsoxB126+t8fw7ySEO48nmDg5COTjxDI65/Y2OWpeEHk3ZOe8zg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chokidar@3.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7VT13fmjotKpGipCW9JEQAusEPE+Ei8nl6/g4FBAmIm0GOOLMua9NDDo/DWp0ZAxCr3cPq5ZpBqmPAQgDda2Pw==}
engines: {node: '>= 8.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chownr@1.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jJ0bqzaylmJtVnNgzTeSOs8DPavpbYgEr/b0YL8/2GO3xJEhInFmhKMUnEJQjZumK7KXGFhUy89PrsJWlakBVg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chownr@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bIomtDF5KGpdogkLd9VspvFzk9KfpyyGlS8YFVZl7TGPBHL5snIOnxeshwVgPteQ9b4Eydl+pVbIyE1DcvCWgQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chromium-pickle-js@0.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1R5Fho+jBq0DDydt+/vHWj5KJNJCKdARKOCwZUen84I5BreWoLqRLANH1U87eJy1tiASPtMnGqJJq0ZsLoRPOw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ci-info@3.9.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NIxF55hv4nSqQswkAeiOi1r83xy8JldOFDTWiug55KBu9Jnblncd2U6ViHmYgHf01TPZS77NJBhBMKdWj9HQMQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cli-truncate@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-n8fOixwDD6b/ObinzTrp1ZKFzbgvKZvuz/TvejnLn1aQfC6r52XEx85FmuC+3HI+JM7coBRXUvNqEU2PHVrHpg==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
client-only@0.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-IV3Ou0jSMzZrd3pZ48nLkT9DA7Ag1pnPzaiQhpW7c3RbcqqzvzzVu+L8gfqMp/8IM2MQtSiqaCxrrcfu8I8rMA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cliui@8.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BSeNnyus75C4//NQ9gQt1/csTXyo/8Sb+afLAkzAptFuMsod9HFokGNudZpi/oQV73hnVK+sR+5PVRMd+Dr7YQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
clone-response@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ROoL94jJH2dUVML2Y/5PEDNaSHgeOdSDicUyS7izcF63G6sTc/FTjLub4b8Il9S8S0beOfYt0TaA5qvFK+w0wA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
clsx@1.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EcR6r5a8bj6pu3ycsa/E/cKVGuTgZJZdsyUYHOksG/UHIiKfjxzRxYJpyVBwYaQeOvghal9fcc4PidlgzugAQg==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
clsx@2.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eYm0QWBtUrBWZWG0d386OGAw16Z995PiOVo2B7bjWSbHedGl5e0ZWaq65kOGgUSNesEIDkB9ISbTg/JK9dhCZA==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
codemirror@6.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-J8j+nZ+CdWmIeFIGXEFbFPtpiYacFMDR8GlHK3IyHQJMCaVRfGx9NT+Hxivv1ckLWPvNdZqndbr/7lVhrf/Svg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
color-convert@1.9.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QfAUtd+vFdAtFQcC8CCyYt1fYWxSqAiK2cSD6zDB8N3cpsEBAvRxp9zOGg6G/SHHJYAT88/az/IuDGALsNVbGg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
color-convert@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RRECPsj7iu/xb5oKYcsFHSppFNnsj/52OVTRKb4zP5onXwVF3zVmmToNcOfGC+CRDpfK/U584fMg38ZHCaElKQ==}
engines: {node: '>=7.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
color-name@1.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-72fSenhMw2HZMTVHeCA9KCmpEIbzWiQsjN+BHcBbS9vr1mtt+vJjPdksIBNUmKAW8TFUDPJK5SUU3QhE9NEXDw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
color-name@1.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dOy+3AuW3a2wNbZHIuMZpTcgjGuLU/uBL/ubcZF9OXbDo8ff4O8yVp5Bf0efS8uEoYo5q4Fx7dY9OgQGXgAsQA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
color-string@1.9.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-shrVawQFojnZv6xM40anx4CkoDP+fZsw/ZerEMsW/pyzsRbElpsL/DBVW7q3ExxwusdNXI3lXpuhEZkzs8p5Eg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
color@4.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1rXeuUUiGGrykh+CeBdu5Ie7OJwinCgQY0bc7GCRxy5xVHy+moaqkpL/jqQq0MtQOeYcrqEz4abc5f0KtU7W4A==}
engines: {node: '>=12.5.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
combined-stream@1.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FQN4MRfuJeHf7cBbBMJFXhKSDq+2kAArBlmRBvcvFE5BB1HZKXtSFASDhdlz9zOYwxh8lDdnvmMOe/+5cdoEdg==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
commander@10.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-y4Mg2tXshplEbSGzx7amzPwKKOCGuoSRP/CjEdwwk0FOGlUbq6lKuoyDZTNZkmxHdJtp54hdfY/JUrdL7Xfdug==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
commander@11.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-yPVavfyCcRhmorC7rWlkHn15b4wDVgVmBA7kV4QVBsF7kv/9TKJAbAXVTxvTnwP8HHKjRCJDClKbciiYS7p0DQ==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
commander@2.20.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GpVkmM8vF2vQUkj2LvZmD35JxeJOLCwJ9cUkugyk2nuhbv3+mJvpLYYt+0+USMxE+oj+ey/lJEnhZw75x/OMcQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
commander@4.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NOKm8xhkzAjzFx8B2v5OAHT+u5pRQc2UCa2Vq9jYL/31o2wi9mxBA7LIFs3sV5VSC49z6pEhfbMULvShKj26WA==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
commander@5.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-P0CysNDQ7rtVw4QIQtm+MRxV66vKFSvlsQvGYXZWR3qFU0jlMKHZZZgw8e+8DSah4UDKMqnknRDQz+xuQXQ/Zg==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
commander@7.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QrWXB+ZQSVPmIWIhtEO9H+gwHaMGYiF5ChvoJ+K9ZGHG/sVsa6yiesAD1GC/x46sET00Xlwo1u49RVVVzvcSkw==}
engines: {node: '>= 10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
comment-parser@1.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-buhp5kePrmda3vhc5B9t7pUQXAb2Tnd0qgpkIhPhkHXxJpiPJ11H0ZEU0oBpJ2QztSbzG/ZxMj/CHsYJqRHmyg==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
compare-version@0.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pJDh5/4wrEnXX/VWRZvruAGHkzKdr46z11OlTPN+VrATlWWhSKewNCJ1futCO5C7eJB3nPMFZA1LeYtcFboZ2A==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
compress-commons@4.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-D3uMHtGc/fcO1Gt1/L7i1e33VOvD4A9hfQLP+6ewd+BvG/gQ84Yh4oftEhAdjSMgBgwGL+jsppT7JYNpo6MHHg==}
engines: {node: '>= 10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
computeds@0.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7CEBgcMjVmitjYo5q8JTJVra6X5mQ20uTThdK+0kR7UEaDrAWEQcRiBtWJzga4eRpP6afNwwLsX2SET2JhVB1Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
concat-map@0.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/Srv4dswyQNBfohGpz9o6Yb3Gz3SrUDqBH5rTuhGR7ahtlbYKnVxw2bCFMRljaA7EXHaXZ8wsHdodFvbkhKmqg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
confbox@0.1.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-uJcB/FKZtBMCJpK8MQji6bJHgu1tixKPxRLeGkNzBoOZzpnZUJm0jm2/sBDWcuBx1dYgxV4JU+g5hmNxCyAmdA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
config-chain@1.1.13:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qj+f8APARXHrM0hraqXYb2/bOVSV4PvJQlNZ/DVj0QrmNM2q2euizkeuVckQ57J+W0mRH6Hvi+k50M4Jul2VRQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
config-file-ts@0.2.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6boGVaglwblBgJqGyxm4+xCmEGcWgnWHSWHY5jad58awQhB6gftq0G8HbzU39YqCIYHMLAiL1yjwiZ36m/CL8w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
connect@3.7.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZqRXc+tZukToSNmh5C2iWMSoV3X1YUcPbqEM4DkEG5tNQXrQUZCNVGGv3IuicnkMtPfGf3Xtp8WCXs295iQ1pQ==}
engines: {node: '>= 0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
connected@0.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-J8DB7618GkIYjc1RCxSdG3vffhhYRwHNEckjOGfwAbabQIMgKsL5c54IaWtisulEwoOEbEODEUak4kyJP2GJ/Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
consola@3.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-I5qxpzLv+sJhTVEoLYNcTW+bThDCPsit0vLNKShZx6rLtpilNpmmeTPaeqJb9ZE9dV3DGaeby6Vuhrw38WjeyQ==}
engines: {node: ^14.18.0 || >=16.10.0}
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
constant-case@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-I2hSBi7Vvs7BEuJDr5dDHfzb/Ruj3FyvFyh7KLilAjNQw3Be+xgqUBA2W6scVEcL0hL1dwPRtIqEPVUCKkSsyQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
content-type@1.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nTjqfcBFEipKdXCv4YDQWCfmcLZKm81ldF0pAopTvyrFGVbcR6P/VAAd5G7N+0tTr8QqiU0tFadD6FK4NtJwOA==}
engines: {node: '>= 0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
convert-source-map@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Kvp459HrV2FEJ1CAsi1Ku+MY3kasH19TFykTz2xWmMeq6bk2NU3XXvfJ+Q61m0xktWwt+1HSYf3JZsTms3aRJg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cookie@0.4.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-aSWTXFzaKWkvHO1Ny/s+ePFpvKsPnjc551iI41v3ny/ow6tBG5Vd+FuqGNhh1LxOmVzOlGUriIlOaokOvhaStA==}
engines: {node: '>= 0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
copy-anything@3.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-yCEafptTtb4bk7GLEQoM8KVJpxAfdBJYaXyzQEgQQQgYrZiDp8SJmGKlYza6CYjEDNstAdNdKA3UuoULlEbS6w==}
engines: {node: '>=12.13'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
core-util-is@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3lqz5YjWTYnW6dlDa5TLaTCcShfar1e40rmcJVwCBJC6mWlFuj0eCHIElmG1g5kyuJ/GD+8Wn4FFCcz4gJPfaQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
core-util-is@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZQBvi1DcpJ4GDqanjucZ2Hj3wEO5pZDS89BWbkcrvdxksJorwUDDZamX9ldFkp9aw2lmBDLgkObEA4DWNJ9FYQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cors@2.8.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KIHbLJqu73RGr/hnbrO9uBeixNGuvSQjul/jdFvS/KFSIH1hWVd1ng7zOHx+YrEfInLG7q4n6GHQ9cDtxv/P6g==}
engines: {node: '>= 0.10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
crc-32@1.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ROmzCKrTnOwybPcJApAA6WBWij23HVfGVNKqqrZpuyZOHqK2CwHSvpGuyt/UNNvaIjEd8X5IFGp4Mh+Ie1IHJQ==}
engines: {node: '>=0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
crc32-stream@4.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NT7w2JVU7DFroFdYkeq8cywxrgjPHWkdX1wjpRQXPX5Asews3tA+Ght6lddQO5Mkumffp3X7GEqku3epj2toIw==}
engines: {node: '>= 10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
crc@3.8.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iX3mfgcTMIq3ZKLIsVFAbv7+Mc10kxabAGQb8HvjA1o3T1PIYprbakQ65d3I+2HGHt6nSKkM9PYjgoJO2KcFBQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
create-servers@3.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bfzggqlfxHxiZ9/U4TmSqXDUIuYnTamYSmEa7DwA487cH4VXqR8yNmgxZCzY7ElipPPSkcaQfn3xhL90RBR4+A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
crelt@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VQ2MBenTq1fWZUH9DJNGti7kKv6EeAuYr3cLwxUWhIu1baTaXh4Ib5W2CqHVqib4/MqbYGJqiL3Zb8GJZr3l4g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cross-env@7.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+/HKd6EgcQCJGh2PSjZuUitQBQynKor4wrFbRg4DtAgS1aWO+gU52xpH7M9ScGgXSYmAVS9bIJ8EzuaGw0oNAw==}
engines: {node: '>=10.14', npm: '>=6', yarn: '>=1'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
cross-spawn@6.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eTVLrBSt7fjbDygz805pMnstIs2VTBNkRm0qxZd+M7A5XDdxVRWO5MxGBXZhjY4cqLYLdtrGqRf8mBPmzwSpWQ==}
engines: {node: '>=4.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cross-spawn@7.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iRDPJKUPVEND7dHPO8rkbOnPpyDygcDFtWjpeWNCgy8WP2rXcxXL8TskReQl6OrB2G7+UJrags1q15Fudc7G6w==}
engines: {node: '>= 8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
css-select@5.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nwoRF1rvRRnnCqqY7updORDsuqKzqYJ28+oSMaJMMgOauh3fvwHqMS7EZpIPqK8GL+g9mKxF1vP/ZjSeNjEVHg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
css-what@6.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HTUrgRJ7r4dsZKU6GjmpfRK1O76h97Z8MfS1G0FozR+oF2kG6Vfe8JE6zwrkbxigziPHinCJ+gCPjA9EaBDtRw==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
css.escape@1.5.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YUifsXXuknHlUsmlgyY0PKzgPOr7/FjCePfHNt0jxm83wHZi44VDMQ7/fGNkjY3/jV1MC+1CmZbaHzugyeRtpg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cssesc@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/Tb/JcjK111nNScGob5MNtsntNM1aCNUDipB/TkwZFhyDrrE47SOx/18wF2bbjgc3ZzCSKW1T5nt5EbFoAz/Vg==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
cssstyle@4.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8ZYiJ3A/3OkDd093CBT/0UKDWry7ak4BdPTFP2+QEP7cmhouyq/Up709ASSj2cK02BbZiMgk7kYjZNS4QP5qrQ==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
csstype@3.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-M1uQkMl8rQK/szD0LNhtqxIPLpimGm8sOBwU7lLnCpSbTyY3yeU1Vc7l4KT5zT4s/yOxHH5O7tIuuLOCnLADRw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
culori@3.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pHJg+jbuFsCjz9iclQBqyL3B2HLCBF71BwVNujUYEvCeQMvV97R59MNK3R2+jgJ3a1fcZgI9B3vYgz8lzr/BFQ==}
engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-array@3.2.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tdQAmyA18i4J7wprpYq8ClcxZy3SC31QMeByyCFyRt7BVHdREQZ5lpzoe5mFEYZUWe+oq8HBvk9JjpibyEV4Jg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-axis@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-IH5tgjV4jE/GhHkRV0HiVYPDtvfjHQlQfJHs0usq7M30XcSBvOotpmH1IgkcXsO/5gEQZD43B//fc7SRT5S+xw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-brush@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ALnjWlVYkXsVIGlOsuWH1+3udkYFI48Ljihfnh8FZPF2QS9o+PzGLBslO0PjzVoHLZ2KCVgAM8NVkXPJB2aNnQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-chord@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VE5S6TNa+j8msksl7HwjxMHDM2yNK3XCkusIlpX5kwauBfXuyLAtNg9jCp/iHH61tgI4sb6R/EIMWCqEIdjT/g==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-color@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zg/chbXyeBtMQ1LbD/WSoW2DpC3I0mpmPdW+ynRTj/x2DAWYrIY7qeZIHidozwV24m4iavr15lNwIwLxRmOxhA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-contour@4.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4EzFTRIikzs47RGmdxbeUvLWtGedDUNkTcmzoeyg4sP/dvCexO47AaQL7VKy/gul85TOxw+IBgA8US2xwbToNA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-delaunay@6.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mdjtIZ1XLAM8bm/hx3WwjfHt6Sggek7qH043O8KEjDXN40xi3vx/6pYSVTwLjEgiXQTbvaouWKynLBiUZ6SK6A==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-dispatch@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rzUyPU/S7rwUflMyLc1ETDeBj0NRuHKKAcvukozwhshr6g6c5d8zh4c2gQjY2bZ0dXeGLWc1PF174P2tVvKhfg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-drag@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pWbUJLdETVA8lQNJecMxoXfH6x+mO2UQo8rSmZ+QqxcbyA3hfeprFgIT//HW2nlHChWeIIMwS2Fq+gEARkhTkg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-dsv@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UG6OvdI5afDIFP9w4G0mNq50dSOsXHJaRE8arAS5o9ApWnIElp8GZw1Dun8vP8OyHOZ/QJUKUJwxiiCCnUwm+Q==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
d3-ease@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wR/XK3D3XcLIZwpbvQwQ5fK+8Ykds1ip7A2Txe0yxncXSdq1L9skcG7blcedkOX+ZcgxGAmLX1FrRGbADwzi0w==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-fetch@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kpkQIM20n3oLVBKGg6oHrUchHM3xODkTzjMoj7aWQFq5QEM+R6E4WkzT5+tojDY7yjez8KgCBRoj4aEr99Fdqw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-force@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zxV/SsA+U4yte8051P4ECydjD/S+qeYtnaIyAs9tgHCqfguma/aAQDjo85A9Z6EKhBirHRJHXIgJUlffT4wdLg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-format@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YyUI6AEuY/Wpt8KWLgZHsIU86atmikuoOmCfommt0LYHiQSPjvX2AcFc38PX0CBpr2RCyZhjex+NS/LPOv6YqA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-geo@3.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-637ln3gXKXOwhalDzinUgY83KzNWZRKbYubaG+fGVuc/dxO64RRljtCTnf5ecMyE1RIdtqpkVcq0IbtU2S8j2Q==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-hierarchy@3.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FX/9frcub54beBdugHjDCdikxThEqjnR93Qt7PvQTOHxyiNCAlvMrHhclk3cD5VeAaq9fxmfRp+CnWw9rEMBuA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-interpolate@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3bYs1rOD33uo8aqJfKP3JWPAibgw8Zm2+L9vBKEHJ2Rg+viTR7o5Mmv5mZcieN+FRYaAOWX5SJATX6k1PWz72g==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-path@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-p3KP5HCf/bvjBSSKuXid6Zqijx7wIfNW+J/maPs+iwR35at5JCbLUT0LzF1cnjbCHWhqzQTIN2Jpe8pRebIEFQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-polygon@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3vbA7vXYwfe1SYhED++fPUQlWSYTTGmFmQiany/gdbiWgU/iEyQzyymwL9SkJjFFuCS4902BSzewVGsHHmHtXg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-quadtree@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-04xDrxQTDTCFwP5H6hRhsRcb9xxv2RzkcsygFzmkSIOJy3PeRJP7sNk3VRIbKXcog561P9oU0/rVH6vDROAgUw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-random@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FXMe9GfxTxqd5D6jFsQ+DJ8BJS4E/fT5mqqdjovykEB2oFbTMDVdg1MGFxfQW+FBOGoB++k8swBrgwSHT1cUXQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-scale-chromatic@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-A3s5PWiZ9YCXFye1o246KoscMWqf8BsD9eRiJ3He7C9OBaxKhAd5TFCdEx/7VbKtxxTsu//1mMJFrEt572cEyQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-scale@4.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GZW464g1SH7ag3Y7hXjf8RoUuAFIqklOAq3MRl4OaWabTFJY9PN/E1YklhXLh+OQ3fM9yS2nOkCoS+WLZ6kvxQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-selection@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fmTRWbNMmsmWq6xJV8D19U/gw/bwrHfNXxrIN+HfZgnzqTHp9jOmKMhsTUjXOJnZOdZY9Q28y4yebKzqDKlxlQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-shape@3.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SaLBuwGm3MOViRq2ABk3eLoxwZELpH6zhl3FbAoJ7Vm1gofKx6El1Ib5z23NUEhF9AsGl7y+dzLe5Cw2AArGTA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-time-format@4.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dJxPBlzC7NugB2PDLwo9Q8JiTR3M3e4/XANkreKSUxF8vvXKqm1Yfq4Q5dl8budlunRVlUUaDUgFt7eA8D6NLg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-time@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VqKjzBLejbSMT4IgbmVgDjpkYrNWUYJnbCGo874u7MMKIWsILRX+OpX/gTk8MqjpT1A/c6HY2dCA77ZN0lkQ2Q==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-timer@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ndfJ/JxxMd3nw31uyKoY2naivF+r29V+Lc0svZxe1JvvIRmi8hUsrMvdOwgS1o6uBHmiz91geQ0ylPP0aj1VUA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3-transition@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ApKvfjsSR6tg06xrL434C0WydLr7JewBB3V+/39RMHsaXTOG0zmt/OAXeng5M5LBm0ojmxJrpomQVZ1aPvBL4w==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
d3-selection: 2 - 3
d3-zoom@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-b8AmV3kfQaqWAuacbPuNbL6vahnOJflOhexLzMMNLga62+/nh0JzvJ0aO/5a5MVgUFGS7Hu1P9P03o3fJkDCyw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
d3@7.9.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-e1U46jVP+w7Iut8Jt8ri1YsPOvFpg46k+K8TpCb0P+zjCkjkPnV7WzfDJzMHy1LnA+wj5pLT1wjO901gLXeEhA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dashdash@1.14.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jRFi8UDGo6j+odZiEpjazZaWqEal3w/basFjQHQEwVtZJGDpxbH1MeYluwCS8Xq5wmLJooDlMgvVarmWfGM44g==}
engines: {node: '>=0.10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
data-urls@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZYP5VBHshaDAiVZxjbRVcFJpc+4xGgT0bK3vzy1HLN8jTO975HEbuYzZJcHoQEY5K1a0z8YayJkyVETa08eNTg==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
data-view-buffer@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0lht7OugA5x3iJLOWFhWK/5ehONdprk0ISXqVFn/NFrDu+cuc8iADFrGQz5BnRK7LLU3JmkbXSxaqX+/mXYtUA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
data-view-byte-length@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4J7wRJD3ABAzr8wP+OcIcqq2dlUKp4DVflx++hs5h5ZKydWMI6/D/fAot+yh6g2tHh8fLFTvNOaVN357NvSrOQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
data-view-byte-offset@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-t/Ygsytq+R995EJ5PZlD4Cu56sWa8InXySaViRzw9apusqsOO2bQP+SbYzAhR0pFKoB+43lYy8rWban9JSuXnA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
de-indent@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-e/1zu3xH5MQryN2zdVaF0OrdNLUbvWxzMbi+iNA6Bky7l1RoP8a2fIbRocyHclXt/arDrrR6lL3TqFD9pMQTsg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
debug@2.6.9:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bC7ElrdJaJnPbAP+1EotYvqZsb3ecl5wi6Bfi6BJTUcNowp6cvspg0jXznRTKDjm/E7AdgFBVeAPVMNcKGsHMA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
supports-color: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
supports-color:
optional: true
debug@3.2.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CFjzYYAi4ThfiQvizrFQevTTXHtnCqWfe7x1AhgEscTz6ZbLbfoLRLPugTQyBth6f8ZERVUSyWHFD/7Wu4t1XQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
supports-color: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
supports-color:
optional: true
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
debug@4.3.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Er2nc/H7RrMXZBFCEim6TCmMk02Z8vLC2Rbi1KEBggpo0fS6l0S1nnapwmIi3yW/+GOJap1Krg4w0Hg80oCqgQ==}
engines: {node: '>=6.0'}
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
supports-color: '*'
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
peerDependenciesMeta:
supports-color:
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
decimal.js@10.4.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VBBaLc1MgL5XpzgIP7ny5Z6Nx3UrRkIViUkPUdtl9aya5amy3De1gsUUSB1g3+3sExYNjCAsAznmukyxCb1GRA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
decompress-response@6.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-aW35yZM6Bb/4oJlZncMH2LCoZtJXTRxES17vE3hoRiowU2kWHaJKFkSBDnDR+cm9J+9QhXmREyIfv0pji9ejCQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deep-eql@4.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SUwdGfqdKOwxCPeVYjwSyRpJ7Z+fhpwIAtmCUdZIWZ/YP5R9WAsyuSgpLVDi9bjWoN2LXHNss/dk3urXtdQxGg==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deep-extend@0.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-LOHxIOaPYdHlJRtCQfDIVZtfw/ufM8+rVj649RIHzcm/vGwQRXFt6OPqIFWsm2XEMrNIEtWR64sY1LEKD2vAOA==}
engines: {node: '>=4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deep-is@0.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oIPzksmTg4/MriiaYGO+okXDT7ztn/w3Eptv/+gSIdMdKsJo0u4CfYNFJPy+4SKMuCqGw2wxnA+URMg3t8a/bQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
default-browser-id@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-A6p/pu/6fyBcA1TRz/GqWYPViplrftcW2gZC9q79ngNCKAeR/X3gcEdXQHl4KNXV+3wgIJ1CPkJQ3IHM6lcsyA==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
default-browser@5.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WY/3TUME0x3KPYdRRxEJJvXRHV4PyPoUsxtZa78lwItwRQRHhd2U9xOscaT/YTf8uCXIAjeJOFBVEh/7FtD8Xg==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
defer-to-connect@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4tvttepXG1VaYGrRibk5EwJd1t4udunSOVMdLSAL6mId1ix438oPwPZMALY41FCijukO1L0twNcGsdzS7dHgDg==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deferred-leveldown@5.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-a59VOT+oDy7vtAbLRCZwWgxu2BaCfd5Hk7wxJd48ei7I+nsg8Orlb9CLG0PMZienk9BSUKgeAqkO2+Lw+1+Ukw==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
define-data-property@1.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rBMvIzlpA8v6E+SJZoo++HAYqsLrkg7MSfIinMPFhmkorw7X+dOXVJQs+QT69zGkzMyfDnIMN2Wid1+NbL3T+A==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
define-lazy-prop@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-N+MeXYoqr3pOgn8xfyRPREN7gHakLYjhsHhWGT3fWAiL4IkAt0iDw14QiiEm2bE30c5XX5q0FtAA3CK5f9/BUg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
define-properties@1.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8QmQKqEASLd5nx0U1B1okLElbUuuttJ/AnYmRXbbbGDWh6uS208EjD4Xqq/I9wK7u0v6O08XhTWnt5XtEbR6Dg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
defu@6.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mEQCMmwJu317oSz8CwdIOdwf3xMif1ttiM8LTufzc3g6kR+9Pe236twL8j3IYT1F7GfRgGcW6MWxzZjLIkuHIg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
delaunator@5.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8nvh+XBe96aCESrGOqMp/84b13H9cdKbG5P2ejQCh4d4sK9RL4371qou9drQjMhvnPmhWl5hnmqbEE0fXr9Xnw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
delayed-stream@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZySD7Nf91aLB0RxL4KGrKHBXl7Eds1DAmEdcoVawXnLD7SDhpNgtuII2aAkg7a7QS41jxPSZ17p4VdGnMHk3MQ==}
engines: {node: '>=0.4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
depd@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-g7nH6P6dyDioJogAAGprGpCtVImJhpPk/roCzdb3fIh61/s/nPsfR6onyMwkCAR/OlC3yBC0lESvUoQEAssIrw==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
destroy@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2sJGJTaXIIaR1w4iJSNoN0hnMY7Gpc/n8D4qSCJw8QqFWXf7cuAgnEHxBpweaVcPevC2l3KpjYCx3NypQQgaJg==}
engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
detect-libc@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pGjwhsmsp4kL2RTz08wcOlGN83otlqHeD/Z5T8GXZB+/YcpQ/dgo+lbU8ZsGxV0HIvqqxo9l7mqYwyYMD9bKDg==}
engines: {node: '>=0.10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
detect-libc@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bwy0MGW55bG41VqxxypOsdSdGqLwXPI/focwgTYCFMbdUiBAxLg9CFzG08sz2aqzknwiX7Hkl0bQENjg8iLByw==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
detect-node@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-T0NIuQpnTvFDATNuHN5roPwSBG83rFsuO+MXXH9/3N1eFbn4wcPjttvjMLEPWJ0RGUYgQE7cGgS3tNxbqCGM7g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
diacritics@1.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wlwEkqcsaxvPJML+rDh/2iS824jbREk6DUMUKkEaSlxdYHeS43cClJtsWglvw2RfeXGm6ohKDqsXteJ5sP5enA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
didyoumean@1.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gxtyfqMg7GKyhQmb056K7M3xszy/myH8w+B4RT+QXBQsvAOdc3XymqDDPHx1BgPgsdAA5SIifona89YtRATDzw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
diff-sequences@29.6.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EjePK1srD3P08o2j4f0ExnylqRs5B9tJjcp9t1krH2qRi8CCdsYfwe9JgSLurFBWwq4uOlipzfk5fHNvwFKr8Q==}
engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dir-compare@3.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-J7/et3WlGUCxjdnD3HAAzQ6nsnc0WL6DD7WcwJb7c39iH1+AWfg+9OqzJNaI6PkBwBvm1mhZNL9iY/nRiZXlPg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dir-glob@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WkrWp9GR4KXfKGYzOLmTuGVi1UWFfws377n9cc55/tb6DuqyF6pcQ5AbiHEshaDpY9v6oaSr2XCDidGmMwdzIA==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
discontinuous-range@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-c68LpLbO+7kP/b1Hr1qs8/BJ09F5khZGTxqxZuhzxpmwJKOgRFHJWIb9/KmqnqHhLdO55aOxFH/EGBvUQbL/RQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dlv@1.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+HlytyjlPKnIG8XuRG8WvmBP8xs8P71y+SKKS6ZXWoEgLuePxtDoUEiH7WkdePWrQ5JBpE6aoVqfZfJUQkjXwA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dmg-builder@24.13.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rcJUkMfnJpfCboZoOOPf4L29TRtEieHNOeAbYPWPxlaBw/Z1RKrRA86dOI9rwaI4tQSc/RD82zTNHprfUHXsoQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dmg-license@1.0.11:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZdzmqwKmECOWJpqefloC5OJy1+WZBBse5+MR88z9g9Zn4VY+WYUkAyojmhzJckH5YbbZGcYIuGAkY5/Ys5OM2Q==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
os: [darwin]
hasBin: true
doctrine@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-35mSku4ZXK0vfCuHEDAwt55dg2jNajHZ1odvF+8SSr82EsZY4QmXfuWso8oEd8zRhVObSN18aM0CjSdoBX7zIw==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dom-serializer@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wIkAryiqt/nV5EQKqQpo3SToSOV9J0DnbJqwK7Wv/Trc92zIAYZ4FlMu+JPFW1DfGFt81ZTCGgDEabffXeLyJg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dom-walk@0.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6QvTW9mrGeIegrFXdtQi9pk7O/nSK6lSdXW2eqUspN5LWD7UTji2Fqw5V2YLjBpHEoU9Xl/eUWNpDeZvoyOv2w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
domelementtype@2.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-OLETBj6w0OsagBwdXnPdN0cnMfF9opN69co+7ZrbfPGrdpPVNBUj02spi6B1N7wChLQiPn4CSH/zJvXw56gmHw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
domhandler@5.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cgwlv/1iFQiFnU96XXgROh8xTeetsnJiDsTc7TYCLFd9+/WNkIqPTxiM/8pSd8VIrhXGTf1Ny1q1hquVqDJB5w==}
engines: {node: '>= 4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
domutils@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-H78uMmQtI2AhgDJjWeQmHwJJ2bLPD3GMmO7Zja/ZZh84wkm+4ut+IUnUdRa8uCGX88DiVx1j6FRe1XfxEgjEZA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dot-case@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Kv5nKlh6yRrdrGvxeJ2e5y2eRUpkUosIW4A2AS38zwSz27zu7ufDwQPi5Jhs3XAlGNetl3bmnGhQsMtkKJnj3w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dotenv-expand@5.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YXQl1DSa4/PQyRfgrv6aoNjhasp/p4qs9FjJ4q4cQk+8m4r6k4ZSiEyytKG8f8W9gi8WsQtIObNmKd+tMzNTmA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dotenv@9.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-I9OvvrHp4pIARv4+x9iuewrWycX6CcZtoAu1XrzPxc5UygMJXJZYmBsynku8IkrJwgypE5DGNjDPmPRhDCptUg==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
eastasianwidth@0.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-I88TYZWc9XiYHRQ4/3c5rjjfgkjhLyW2luGIheGERbNQ6OY7yTybanSpDXZa8y7VUP9YmDcYa+eyq4ca7iLqWA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
easy-stack@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wK2sCs4feiiJeFXn3zvY0p41mdU5VUgbgs1rNsc/y5ngFUijdWd+iIN8eoyuZHKB8xN6BL4PdWmzqFmxNg6V2w==}
engines: {node: '>=6.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ecc-jsbn@0.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eh9O+hwRHNbG4BLTjEl3nw044CkGm5X6LoaCf7LPp7UU8Qrt47JYNi6nPX8xjW97TKGKm1ouctg0QSpZe9qrnw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
editorconfig@1.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-L9Qe08KWTlqYMVvMcTIvMAdl1cDUubzRNYL+WfA4bLDMHe4nemKkpmYzkznE1FwLKu0EEmy6obgQKzMJrg4x9Q==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
ee-first@1.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WMwm9LhRUo+WUaRN+vRuETqG89IgZphVSNkdFgeb6sS/E4OrDIN7t48CAewSHXc6C8lefD8KKfr5vY61brQlow==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ejs@3.1.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UeJmFfOrAQS8OJWPZ4qtgHyWExa088/MtK5UEyoJGFH67cDEXkZSviOiKRCZ4Xij0zxI3JECgYs3oKx+AizQBA==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
electron-builder-squirrel-windows@24.13.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oHkV0iogWfyK+ah9ZIvMDpei1m9ZRpdXcvde1wTpra2U8AFDNNpqJdnin5z+PM1GbQ5BoaKCWas2HSjtR0HwMg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
electron-builder@24.13.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-yZSgVHft5dNVlo31qmJAe4BVKQfFdwpRw7sFp1iQglDRCDD6r22zfRJuZlhtB5gp9FHUxCMEoWGq10SkCnMAIg==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
electron-is-dev@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3X99K852Yoqu9AcW50qz3ibYBWY79/pBhlMCab8ToEWS48R0T9tyxRiQhwylE7zQdXrMnx2JKqUJyMPmt5FBqA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
electron-publish@24.13.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2ZgdEqJ8e9D17Hwp5LEq5mLQPjqU3lv/IALvgp+4W8VeNhryfGhYEQC/PgDPMrnWUp+l60Ou5SJLsu+k4mhQ8A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
electron-to-chromium@1.5.16:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2gQpi2WYobXmz2q23FrOBYTLcI1O/P4heW3eqX+ldmPVDQELRqhiebV380EhlGG12NtnX1qbK/FHpN0ba+7bLA==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Even more dashboard fixes (#10541) - Fix https://github.com/enso-org/cloud-v2/issues/1383 - Fix file download - both on Electron, and in browser - Refresh versions list when uploading neww file version - Fix app crashing when asset is opened in asset panel while switching to Local Backend - Don't show asset id when asset is opened in asset panel, but user is on the Local backend, resulting in the internal Asset ID being shown - Fix drag-n-drop - :warning: `npm run dev` is NOT fixed in this PR - however it should already be fixed in another PR which has already been merged. This needs testing to confirm whether it is fixed though. Other changes: - Add support for "duplicate project" endpoint on Local Backend - Fix downloading project from nested directory on Local Backend (not working) - Refactor more E2E tests to use the "new" architecture - Simplify "new" E2E architecture to minimize boilerplate # Important Notes - When testing downloads, both Electron and browser should be tested as they use completely separate implementations for how files are downloaded.
2024-07-16 12:55:45 +03:00
electron@31.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5w+kjOsGiTXytPSErBPNp/3znnuEMKc42RD41MqRoQkiYaR8x/Le2+qWk1cL60UwE/67oeKnOHnnol8xEuldGg==}
engines: {node: '>= 12.20.55'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
emoji-regex@8.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MSjYzcWNOA0ewAHpz0MxpYFvwg6yjy1NG3xteoqz644VCo/RPgnr1/GGt+ic3iJTzQ8Eu3TdM14SawnVUmGE6A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
emoji-regex@9.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-L18DaJsXSUk2+42pv8mLs5jJT2hqFkFE4j21wOmgbUqsZ2hL72NsUU785g9RXgo3s0ZNgVl42TiHp3ZtOv/Vyg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
encodeurl@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TPJXq8JqFaVYm2CWmPvnP2Iyo4ZSM7/QKcSmuMLDObfpH5fi7RUGmd/rTDf+rut/saiDiQEeVTNgAmJEdAOx0w==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
encoding-down@6.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QKrV0iKR6MZVJV08QY0wp1e7vF6QbhnbQhb07bwpEyuz4uZiZgPlEGdkCROuFkUwdxlFaiPIhjyarH1ee/3vhw==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
end-of-stream@1.4.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+uw1inIHVPQoaVuHzRyXd21icM+cnt4CzD5rW+NC1wjOUSTOs+Te7FOv7AhN7vS9x/oIyhLP5PR1H+phQAHu5Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
entities@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hCx1oky9PFrJ611mf0ifBLBRW8lUUVRlFolb5gWRfIELabBlbp9xZvrqZLZAs+NxFnbfQoeGd8wDkygjg7U85w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
entities@4.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-V0hjH4dGPh9Ao5p0MoRY6BVqtwCjhz6vI5LT8AJ55H+4g9/4vbHx1I54fS0XuclLhDHArPQCiMjDxjaL8fPxhw==}
engines: {node: '>=0.12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
env-paths@2.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+h1lkLKhZMTYjog1VEpJNG7NZJWcuc2DDk/qsqSTRRCOXiLjeQ1d1/udrUGhqMxUgAlwKNZ0cf2uqan5GLuS2A==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
err-code@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2bmlRpNKBxT/CRmPOlyISQpNj+qSeYvcym/uT0Jx2bMOlKLtSy1ZmLuVxSEKKyor/N5yhvp/ZiG1oE3DEYMSFA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
errno@0.1.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dJ6oBr5SQ1VSd9qkk7ByRgb/1SH4JZjCHSW/mr63/QcXO9zLVxvJ6Oy13nio03rxpSnVDDjFor75SjVeZWPW/A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
error-ex@1.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7dFHNmqeFSEt2ZBsCriorKnn3Z2pj+fd9kmI6QoWw4//DL+icEBfc0U7qJCisqrTsKTjw4fNFy2pW9OqStD84g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
error-stack-parser-es@0.1.5:
resolution: {integrity: sha512-xHku1X40RO+fO8yJ8Wh2f2rZWVjqyhb1zgq1yZ8aZRQkv6OOKhKWRUaht3eSCUbAOBaKIgM+ykwFLE+QUxgGeg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
errs@0.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-r+/tydov04FSwTi+PrGd0IdY195Y1jZW2g27TJ+cErU8vvr9V4hHYxtRF8bMjv4zYEhap7wK7zBQ2i99LRo6kA==}
engines: {node: '>= 0.4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-abstract@1.23.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-e+HfNH61Bj1X9/jLc5v1owaLYuHdeHHSQlkhCBiTK8rBvKaULl/beGMxwrMXjpYrv4pz22BlY570vVePA2ho4A==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-define-property@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jxayLKShrEqqzJ0eumQbVhTYQM27CfT1T35+gCgDFoL82JLsXqTJ76zv6A0YLOgEnLUMvLzsDsGIrl8NFpT2gQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-errors@1.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Zf5H2Kxt2xjTvbJvP2ZWLEICxA6j+hAmMzIlypy4xcBg1vKVnx89Wy0GbS+kf5cwCVFFzdCFh2XSCFNULS6csw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-iterator-helpers@1.0.19:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zoMwbCcH5hwUkKJkT8kDIBZSz9I6mVG//+lDCinLCGov4+r7NIy0ld8o03M0cJxl2spVf6ESYVS6/gpIfq1FFw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
es-module-lexer@1.5.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MVNK56NiMrOwitFB7cqDwq0CQutbw+0BvLshJSse0MUNU+y1FC3bUS/AQg7oUng+/wKrrki7JfmwtVHkVfPLlw==}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-object-atoms@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MZ4iQ6JwHOBQjahnjwaC1ZtIBH+2ohjamzAO3oaHcXYup7qxjF2fixyH+Q71voWHeOkI2q/TnJao/KfXYIZWbw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-set-tostringtag@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3T8uNMC3OQTHkFUsFq8r/BwAXLHvU/9O9mE0fBc/MY5iq/8H7ncvO947LmYA6ldWw9Uh8Yhf25zu6n7nML5QWQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-shim-unscopables@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-J3yBRXCzDu4ULnQwxyToo/OjdMx6akgVC7K6few0a7F/0wLtmKKN7I73AH5T2836UuXRqN7Qg+IIUw/+YJksRw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-to-primitive@1.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QCOllgZJtaUo9miYBcLChTUaHNjJF3PYs1VidD7AwiEj1kYxKeQTctLAezAOH5ZKRH0g2IgPn6KwB4IT8iRpvA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es6-error@4.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Um/+FxMr9CISWh0bi5Zv0iOD+4cFh5qLeks1qhAopKVAJw3drgKbKySikp7wGhDL0HPeaja0P5ULZrxLkniUVg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es6-promise@3.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SOp9Phqvqn7jtEUxPWdWfWoLmyt2VaJ6MpvP9Comy1MceMXqE6bxvaTu4iaxpYYPzhny28Lc+M87/c2cPK6lDg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esbuild-plugin-wasm@1.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0bQ6+1tUbySSnxzn5jnXHMDvYnT0cN/Wd4Syk8g/sqAIJUg7buTIi22svS3Qz6ssx895NT+TgLPb33xi1OkZig==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esbuild@0.21.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mg3OPMV4hXywwpoDxu3Qda5xCKQi+vCTZq8S9J/EpkhB2HzKXq4SNFZE3+NK93JYxc8VMSep+lOUSC/RVKaBqw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esbuild@0.23.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1lvV17H2bMYda/WaFb2jLPeHU3zml2k4/yagNMG8Q/YtfMjCwEUZa2eXXMgZTVSL5q1n4H7sQ0X6CdJDqqeCFA==}
engines: {node: '>=18'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
hasBin: true
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
escalade@3.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WUj2qlxaQtO4g6Pq5c29GTcWGDyd8itL8zTlipgECz3JesAiiOKotd8JU6otB3PACgG6xkJUyVhboMS+bje/jA==}
engines: {node: '>=6'}
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
escape-html@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NiSupZ4OeuGwr68lGIeym/ksIZMJodUGOSCZ/FSnTxcrekbvqrgdUxlJOMpijaKZVjAJrWrGs/6Jy8OMuyj9ow==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
escape-string-regexp@1.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vbRorB5FUQWvla16U8R/qgaFIya2qGzwDrNmCZuYKrbdSUMG6I1ZCGQRefkRVhuOkIGVne7BQ35DSfo1qvJqFg==}
engines: {node: '>=0.8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
escape-string-regexp@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TtpcNJ3XAzx3Gq8sWRzJaVajRs0uVxA2YAkdb1jm2YkPz4G6egUFAyA3n5vtEIZefPk5Wa4UXbKuS5fKkJWdgA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
eslint-config-prettier@9.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NSWl5BFQWEPi1j4TjVNItzYV7dZXZ+wP6I6ZhrBGpChQhZRUaElihE9uRRkcbRnNb76UMKDF3r+WTmNcGPKsqw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
eslint: '>=7.0.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-plugin-jsdoc@50.4.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-uWtwFxGRv6B8sU63HZM5dAGDhgsatb+LONwmILZJhdRALLOkCX2HFZhdL/Kw2ls8SQMAVEfK+LmnEfxInRN8HA==}
engines: {node: '>=18'}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
peerDependencies:
eslint: ^7.0.0 || ^8.0.0 || ^9.0.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint-plugin-prettier@5.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gH3iR3g4JfF+yYPaJYkN7jEl9QbweL/YfkoRlNnuIEHEz1vHVlCmWOS+eGGiRuzHQXdJFCOTxRgvju9b8VUmrw==}
engines: {node: ^14.18.0 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/eslint': '>=8.0.0'
eslint: '>=8.0.0'
eslint-config-prettier: '*'
prettier: '>=3.0.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/eslint':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
eslint-config-prettier:
optional: true
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
eslint-plugin-react-compiler@19.0.0-beta-8a03594-20241020:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bYg1COih1s3r14IV/AKdQs/SN7CQmNI0ZaMtPdgZ6gp1S1Q/KGP9P43w7R6dHJ4wYpuMBvekNJHQdVu+x6UM+A==}
engines: {node: ^14.17.0 || ^16.0.0 || >= 18.0.0}
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
eslint: '>=7'
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-plugin-react-hooks@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hIOwI+5hYGpJEc4uPRmz2ulCjAGD/N13Lukkh8cLV0i2IRk/bdZDYjgLVHj+U9Z704kLIdIO6iueGvxNur0sgw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: ^3.0.0 || ^4.0.0 || ^5.0.0 || ^6.0.0 || ^7.0.0 || ^8.0.0-0 || ^9.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint-plugin-react@7.37.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xwTnwDqzbDRA8uJ7BMxPs/EXRB3i8ZfnOIp8BsxEQkT0nHPp+WWceqGgo6rKb9ctNi8GJLDT4Go5HAWELa/WMg==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
eslint: ^3 || ^4 || ^5 || ^6 || ^7 || ^8 || ^9.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-plugin-vue@9.29.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MH/MbVae4HV/tM8gKAVWMPJbYgW04CK7SuzYRrlNERpxbO0P3+Zdsa2oAcFBW6xNu7W6lIkGOsFAMCRTYmrlWQ==}
engines: {node: ^14.17.0 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
eslint: ^6.2.0 || ^7.0.0 || ^8.0.0 || ^9.0.0
eslint-scope@7.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dOt21O7lTMhDM+X9mB4GX+DZrZtCUJPL/wlcTqxyrx5IvO0IYtILdtrQGQp+8n5S0gwSVmOf9NQrjMOgfQZlIg==}
engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-scope@8.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-14dSvlhaVhKKsa9Fx1l8A17s7ah7Ef7wCakJ10LYk6+GYmP9yDti2oq2SEwcyndt6knfcZyhyxwY3i9yL78EQw==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
eslint-visitor-keys@3.4.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wpc+LXeiyiisxPlEkUzU6svyS1frIO3Mgxj1fdy7Pm8Ygzguax2N3Fa/D/ag1WqbOprdI+uY6wMUl8/a2G+iag==}
engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-visitor-keys@4.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Q7lok0mqMUSf5a/AdAZkA5a/gHcO6snwQClVNNvFKCAVlxXucdU8pKydU5ZVZjBx5xr37vGbFFWtLQYreLzrZg==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint@9.13.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EYZK6SX6zjFHST/HRytOdA/zE72Cq/bfw45LSyuwrdvcclb/gqV8RRQxywOBEWO2+WDpva6UZa4CcDeJKzUCFA==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
jiti: '*'
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
peerDependenciesMeta:
jiti:
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
espree@10.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-upbkBJbckcCNBDBDXEbuhjbP68n+scUd3k/U2EkyM9nw+I/jPiL4cLF/Al06CF96wRltFda16sxDFrxsI1v0/g==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
espree@9.6.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oruZaFkjorTpF32kDSI5/75ViwGeZginGGy2NoOSg3Q9bnwlnmDm4HLnkl0RE3n+njDXR037aY1+x58Z/zFdwQ==}
engines: {node: ^12.22.0 || ^14.17.0 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esprima@4.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eGuFFw7Upda+g4p+QHvnW0RyTX/SVeJBDM/gCtMARO0cLuT2HcEKnTPvhjV6aGeqrCB/sbNop0Kszm0jsaWU4A==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
esquery@1.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ca9pw9fomFcKPvFLXhBKUK90ZvGibiGOvRJNbjljY7s7uq/5YO4BOzcYtJqExdx99rF6aAcnRxHmcUHcz6sQsg==}
engines: {node: '>=0.10'}
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esrecurse@4.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KmfKL3b6G+RXvP8N1vr3Tq1kL/oCFgn2NYXEtqP8/L3pKapUA4G8cFVaoF3SU323CD4XypR/ffioHmkti6/Tag==}
engines: {node: '>=4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
estraverse@5.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MMdARuVEQziNTeJD8DgMqmhwR11BRQ/cBP+pLtYdSTnf3MIO8fFeiINEbX36ZdNlfU/7A9f3gUw49B3oQsvwBA==}
engines: {node: '>=4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
estree-walker@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Rfkk/Mp/DL7JVje3u18FxFujQlTNR2q6QfMSMB7AvCBx91NGj/ba3kCfza0f6dVDbw7YlRf/nDrn7pQrCCyQ/w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
estree-walker@3.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7RUKfXgSMMkzt6ZuXmqapOurLGPPfgj6l9uRZ7lRGolvk0y2yocc35LdcxKC5PQZdn2DMqioAQ2NoWcrTKmm6g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esutils@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kVscqXk4OCp68SZ0dkgEKVi6/8ij300KBWTJq32P/dYeWTSwK41WyTxalN1eRmA5Z9UU/LX9D7FWSmV9SAYx6g==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
event-pubsub@4.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-z7IyloorXvKbFx9Bpie2+vMJKKx1fH1EN5yiTfp8CiLOTptSYy1g8H4yDpGlEdshL1PBiFtBHepF2cNsqeEeFQ==}
engines: {node: '>=4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
event-target-shim@6.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8q3LsZjRezbFZ2PN+uP+Q7pnHUMmAOziU2vA2OwoFaKIXxlxl38IylhSSgUorWu/rf4er67w0ikBqjBFk/pomA==}
engines: {node: '>=10.13.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
events@3.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mQw+2fkQbALzQ7V0MY0IqdnXNOeTtP4r0lN9z7AAawCXgqea7bDii20AYrIBrFd/Hx0M2Ocz6S111CaFkUcb0Q==}
engines: {node: '>=0.8.x'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
execa@8.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VyhnebXciFV2DESc+p6B+y0LjSm0krU4OgJN44qFAhBY0TJ+1V61tYD2+wHusZ6F9n5K+vl8k0sTy7PEfV4qpg==}
engines: {node: '>=16.17'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
exif-parser@0.1.12:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-c2bQfLNbMzLPmzQuOr8fy0csy84WmwnER81W88DzTp9CYNPJ6yzOj2EZAh9pywYpqHnshVLHQJ8WzldAyfY+Iw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
expand-template@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XYfuKMvj4O35f/pOXLObndIRvyQ+/+6AhODh+OKWj9S9498pHHn/IMszH+gt0fBCRWMNfk1ZSp5x3AifmnI2vg==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
extend-shallow@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zCnTtlxNoAiDc3gqY2aYAWFx7XWWiasuF2K8Me5WbN8otHKTUKBwjPtNpRs/rbUZm7KxWAaNj7P1a/p52GbVug==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
extend@3.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fjquC59cD7CyW6urNXK0FBufkZcoiGG80wTuPujX590cB5Ttln20E2UB4S/WARVqhXffZl2LNgS+gQdPIIim/g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
extract-zip@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GDhU9ntwuKyGXdZBUgTIe+vXnWj0fppUEtMDL0+idd5Sta8TGpHssn/eusA9mrPr9qNDym6SxAYZjNvCn/9RBg==}
engines: {node: '>= 10.17.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
extsprintf@1.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-11Ndz7Nv+mvAC1j0ktTa7fAb0vLyGGX+rMHNBYQviQDGU0Hw7lhctJANqbPhu9nV9/izT/IntTgZ7Im/9LJs9g==}
engines: {'0': node >=0.6.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
extsprintf@1.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Wrk35e8ydCKDj/ArClo1VrPVmN8zph5V4AtHwIuHhvMXsKf73UT3BOD+azBIW+3wOJ4FhEH7zyaJCFvChjYvMA==}
engines: {'0': node >=0.6.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-base64-decode@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qwaScUgUGBYeDNRnbc/KyllVU88Jk1pRHPStuF/lO7B0/RTRLj7U0lkdTAutlBblY08rwZDff6tNU9cjv6j//Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-check@3.19.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CO2JX/8/PT9bDGO1iXa5h5ey1skaKI1dvecERyhH4pp3PGjwd3KIjMAXEg79Ps9nclsdt4oPbfqiAnLU0EwrAQ==}
engines: {node: '>=8.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-deep-equal@3.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-f3qQ9oQy9j2AhBe/H9VC91wLmKBCCU/gDOnKNAYG5hswO7BLKj09Hc5HYNz9cGI++xlpDCIgDaitVs03ATR84Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-diff@1.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VxPP4NqbUjj6MaAOafWeUn2cXWLcCtljklUtZf0Ind4XQ+QPtmA0b18zZy0jIQx+ExRVCR/ZQpBmik5lXshNsw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-glob@3.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oX2ruAFQwf/Orj8m737Y5adxDQO0LAB7/S5MnxCdTNDd4p6BsyIVsv9JQsATbTSq8KHRpLwIHbVlUNatxd+1Ow==}
engines: {node: '>=8.6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-json-stable-stringify@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-lhd/wF+Lk98HZoTCtlVraHtfh5XYijIjalXck7saUtuanSDyLMxnHhSXEDJqHxD7msR8D0uCmqlkwjCV8xvwHw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-levenshtein@2.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DCXu6Ifhqcks7TZKY3Hxp3y6qphY5SJZmrWMDrKcERSOXWQdMhU9Ig/PYrzyw/ul9jOIyh0N4M0tbC5hodg8dw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-safe-stringify@2.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-W+KJc2dmILlPplD/H4K9l9LcAHAfPtP6BY84uVLXQ6Evcz9Lcg33Y2z1IVblT6xdY54PXYVHEv+0Wpq8Io6zkA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fastq@1.17.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sRVD3lWVIXWg6By68ZN7vho9a1pQcN/WBFaAAsDDFzlJjvoGx0P8z7V1t72grFJfJhu3YPZBuu25f7Kaw2jN1w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fd-slicer@1.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cE1qsB/VwyQozZ+q1dGxR8LBYNZeofhEdUNGSMbQD3Gw2lAzX9Zb3uIU6Ebc/Fmyjo9AWWfnn0AUCHqtevs/8g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
file-entry-cache@8.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XXTUwCvisa5oacNGRP9SfNtYBNAMi+RPwBFmblZEF7N7swHYQS6/Zfk7SRwx4D5j3CH211YNRco1DEMNVfZCnQ==}
engines: {node: '>=16.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
file-type@3.9.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RLoqTXE8/vPmMuTI88DAzhMYC99I8BWv7zYP4A1puo5HIjEJ5EX48ighy4ZyKMG9EDXxBgW6e++cn7d1xuFghA==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
filelist@1.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-w1cEuf3S+DrLCQL7ET6kz+gmlJdbq9J7yXCSjK/OZCPA+qEN1WyF4ZAf0YYJa4/shHJra2t/d/r8SV4Ji+x+8Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fill-range@7.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qOo9F+dMUmC2Lcb4BbVvnKJxTPjCm+RRpe4gDuGrzkL7mEVl/djYSu2OdQ2Pa302N4oqkSg9ir6jaLWJ2USVpQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
finalhandler@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-aAWcW57uxVNrQZqFXjITpW3sIUQmHGG3qSb9mUah9MgMC4NeWhNOlNjXEYq3HjRAvL6arUviZGGJsBg6z0zsWA==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
find-up@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-78/PXT1wlLLDgTzDs7sjq9hzz0vXD+zn+7wypEe4fXQxCmdmqfGsEPQxmiCSQI3ajFV91bVSsvNtrJRiW6nGng==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
flat-cache@4.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-f7ccFPK3SXFHpx15UIGyRJ/FJQctuKZ0zVuN3frBo4HnK3cay9VEW0R6yPYFHC0AgqhukPzKjq22t5DmAyqGyw==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
flatted@3.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-X8cqMLLie7KsNUDSdzeN8FYK9rEt4Dt67OsG/DNGnYTSDBG4uFAJFBnUeiV+zCVAvwFy56IjM9sH51jVaEhNxw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
flexsearch@0.7.21:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-W7cHV7Hrwjid6lWmy0IhsWDFQboWSng25U3VVywpHOTJnnAZNPScog67G+cVpeX9f7yDD21ih0WDrMMT+JoaYg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
floating-vue@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YSffLYOjoaaPPBZc7VQR2qMCQ7xeXuh7i8a2u8WOdSmkjTtKtZpj2aaJnLtZRHmehrMHyCgtSxLu8jFNNX2sVw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nuxt/kit': ^3.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vue: ^3.2.0
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nuxt/kit':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
for-each@0.3.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jqYfLp7mo9vIyQf8ykW2v7A+2N4QjeCeI5+Dz9XraiO1ign81wjiH7Fb9vSOWvQfNtmSa4H2RoQTrrXivdUZmw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
foreground-child@3.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PXUUyLqrR2XCWICfv6ukppP96sdFwWbNEnfEMt7jNsISjMsvaLNinAHNDYyvkyU+SZG2BTSbT5NjG+vZslfGTA==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
forever-agent@0.6.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-j0KLYPhm6zeac4lz3oJ3o65qvgQCcPubiyotZrXqEaG4hNagNYO8qdlUrX5vwqv9ohqeT/Z3j6+yW067yWWdUw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
form-data@2.3.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1lLKB2Mu3aGP1Q/2eCOx0fNbRMe7XdwktwOruhfqqd0rIJWwN4Dh+E3hrPSlDCXnSR7UtZ1N38rVXm+6+MEhJQ==}
engines: {node: '>= 0.12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
form-data@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RHkBKtLWUVwd7SqRIvCZMEvAMoGUp0XU+seQiZejj0COz3RI3hWP4sCv3gZWWLjJTd7rGwcsF5eKZGii0r/hbg==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
form-data@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ETEklSGi5t0QMZuiXoA/Q6vcnxcLQP5vdugSpuAyi6SVGi2clPPp+xgEhuMaHC+zGgn31Kd235W35f7Hykkaww==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
format-util@1.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-varLbTj0e0yVyRpqQhuWV+8hlePAgaoFRhNFj50BNjEIrw1/DphHSObtqwskVCPWNgzwPoQrZAbfa/SBiicNeg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
framer-motion@11.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hjYjMUQaWuqilwRr5kC0CunHZFVMtKWHy/IdL/LPRBD0C491DKTvYwQRJ5qRXEAOT+Rth7Vi4XBe4TA4bFOn3A==}
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@emotion/is-prop-valid': '*'
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
react: ^18.0.0
react-dom: ^18.0.0
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@emotion/is-prop-valid':
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
optional: true
react:
optional: true
react-dom:
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-constants@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-y6OAwoSIf7FyjMIv94u+b5rdheZEjzR63GTyZJm5qh4Bi+2YgwLCcI/fPFZkL5PSixOt6ZNKm+w+Hfp/Bciwow==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra@10.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oRXApq54ETRj4eMiFzGnHWGy+zo5raudjuxN0b8H7s/RU2oW0Wvsx9O0ACRN/kRq9E8Vu/ReskGB5o3ji+FzHQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra@11.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PmDi3uwK5nFuXh7XDTlVnS17xJS7vW36is2+w3xcv8SVxiB4NyATf4ctkVY5bkSjX0Y4nbvZCq1/EjtEyr9ktw==}
engines: {node: '>=14.14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra@7.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YJDaCJZEnBmcbw13fvdAM9AwNOJwOzrE4pqMqBq5nFiEqXUqHwlK4B+3pUw6JNvfSPtX05xFHtYy/1ni01eGCw==}
engines: {node: '>=6 <7 || >=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra@8.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-yhlQgA6mnOJUKOsRUFsgJdQCvkKhcz8tlZG5HBQfReYZy46OwLcY+Zia0mtdHsOo9y/hP+CxMN0TU9QxoOtG4g==}
engines: {node: '>=6 <7 || >=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra@9.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hcg3ZmepS30/7BSFqRvoo3DOMQu7IjqxO5nCDt+zM9XWjb33Wg7ziNT+Qvqbuc3+gWpzO02JubVyk2G4Zvo1OQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-minipass@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-V/JgOLFCS+R6Vcq0slCuaeWEdNC3ouDlJMNIsacH2VtALiu9mV4LPrHc5cDl8k5aw6J8jwgWWpiTo5RYhmIzvg==}
engines: {node: '>= 8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs.realpath@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-OO0pH2lK6a0hZnAdau5ItzHPI6pUlvI7jMVnxUQRtw4owF2wk8lOSabtGDCTP4Ggrg2MbGnWO9X8K1t4+fGMDw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fsevents@2.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xiqMQR4xAeHTuB9uWm+fFRcIOgKBMiOBP+eXiyT7jsgVCq1bkVygt00oASowB7EdtpOHaaPgKt812P9ab+DDKA==}
engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
os: [darwin]
fsevents@2.3.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5xoDfX+fL7faATnagmWPpbFtwh/R77WmMMqqHGS65C3vvB0YHrgF+B1YmZ3441tMj5n63k0212XNoJwzlhffQw==}
engines: {node: ^8.16.0 || ^10.6.0 || >=11.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
os: [darwin]
function-bind@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7XHNxH7qX9xG5mIwxkhumTox/MIRNcOgDrxWsMt2pAr23WHp6MrRlN7FBSFpCpr+oVO0F744iUgR82nJMfG2SA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
function.prototype.name@1.1.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Z5kx79swU5P27WEayXM1tBi5Ze/lbIyiNgU3qyXUOf9b2rgXYyF9Dy9Cx+IQv/Lc8WCG6L82zwUPpSS9hGehIg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
functions-have-names@1.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xckBUXyTIqT97tq2x2AMb+g163b5JFysYk0x4qxNFwbfQkmNZoiRHb6sPzI9/QV33WeuvVYBUIiD4NzNIyqaRQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
gensync@1.0.0-beta.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3hN7NaskYvMDLQY55gnW3NQ+mesEAepTqlg+VEbj7zzqEMBVNhzcGYYeqFo/TlYz6eQiFcp1HcsCZO+nGgS8zg==}
engines: {node: '>=6.9.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-caller-file@2.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DyFP3BM/3YHTQOCUL/w0OZHR0lpKeGrxotcHWcqNEdnltqFwXVfhEBQ94eIo34AfQpo0rGki4cyIiftY06h2Fg==}
engines: {node: 6.* || 8.* || >= 10.*}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-func-name@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8vXOvuE167CtIc3OyItco7N/dpRtBbYOsPsXCz7X/PMnlGjYjSGuZJgM1Y7mmew7BKf9BqvLX2tnOVy1BBUsxQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-intrinsic@1.2.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5uYhsJH8VJBTv7oslg4BznJYhDoRI6waYCxMmCdnTrcCrHA/fCFKoTFz2JKKE0HdDFUF7/oQuhzumXJK7paBRQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-stdin@8.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sY22aA6xchAzprjyqmSEQv4UbAAzRN0L2dQB0NlN5acTTK9Don6nhoc3eAbUnpZiCANAMfd/+40kVdKfFygohg==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-stream@2.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AUGhbbemXxrZJRD5cDvKtQxLuYaIbNtDTK8YqupCI393Q2KSTreEsLUN3ZxAWFGiKTzL6nKuzfcIvieflUX9qA==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-stream@5.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nBF+F1rAZVCu/p7rjzgA+Yb4lfYXrpl7a6VmJrU8wF9I1CKvP/QwPNZHnOlwbTkY6dvtFIzFMSyQXbLoTQPRpA==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-stream@8.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VaUJspBffn/LMCJVoMvSAdmscJyS1auj5Zulnn5UoYcY531UWmdwhRWkcGKnGU93m5HSXP9LP2usOryrBtQowA==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-symbol-description@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-g0QYk1dZBxGwk+Ngc+ltRH2IBp2f7zBkBMBJZCDerh6EhlhSR6+9irMCuT/09zD6qkarHUSn529sK/yL4S27mg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-tsconfig@4.7.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZCuZCnlqNzjb4QprAzXKdpp/gh6KTxSJuw3IBsPnV/7fV4NxC9ckB+vPTt8w7fJA0TaSD7c55BR47JD6MEDyDw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
getpass@0.1.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0fzj9JxOLfJ+XGLhR8ze3unN0KZCgZwiSSDz168VERjK8Wl8kVSdcu2kspd4s4wtAa1y/qrVRiAA0WclVsu0ng==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
github-from-package@0.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SyHy3T1v2NUXn29OsWdxmK6RwHD+vkj3v8en8AOBZ1wBQ/hCAQ5bAQTD02kW4W9tUp/3Qh6J8r9EvntiyCmOOw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
glob-parent@5.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AOIgSQCepiJYwP3ARnGx+5VnTu2HBYdzbGP45eLw1vr3zB3vZLeyed1sC9hnbcOc9/SrMyM5RPQrkGz4aS9Zow==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
glob-parent@6.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XxwI8EOhVQgWp6iDL+3b0r86f4d6AX6zSU55HfB4ydCEuXLXc5FcYeOu+nnGftS4TEju/11rt4KJPTMgbfmv4A==}
engines: {node: '>=10.13.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
glob@10.4.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GwMlUF6PkPo3Gk21UxkCohOv0PLcIXVtKyLlpEI28R/cO/4eNOdmLk3CMW1wROV/WR/EsZOWAfBbBOqYvs88/w==}
engines: {node: '>=16 || 14 >=14.18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
glob@11.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9UiX/Bl6J2yaBbxKoEBRm4Cipxgok8kQYcOPEhScPwebu2I0HoQOuYdIO6S3hLuWoZgpDpwQZMzTFxgpkyT76g==}
engines: {node: 20 || >=22}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
hasBin: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
glob@7.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nFR0zLpU2YCaRxwoCJvL6UvCH2JFyFVIvwTLsIf21AuHlMskA1hhTdk+LlYJtOlYt9v6dvszD2BGRqBL+iQK9Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: Glob versions prior to v9 are no longer supported
global-agent@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PT6XReJ+D07JvGoxQMkT6qji/jVNfX/h364XHZOWeRzy64sSFr+xJ5OX7LI3b4MPQzdL4H8Y8M0xzPpsVMwA8Q==}
engines: {node: '>=10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
global@4.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wv/LAoHdRE3BeTGz53FAamhGlPLhlssK45usmGFThIi4XqnBmjKQ16u+RNbP7WvigRZDxUsM0J3gcQ5yicaL0w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
globals@11.12.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WOBp/EEGUiIsJSp7wcv/y6MO+lV9UoncWqxuFfm8eBwzWNgyfBd6Gz+IeKQ9jCmyhoH99g15M3T+QaVHFjizVA==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
globals@13.24.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AhO5QUcj8llrbG09iWhPU2B204J1xnPeL8kQmVorSsy+Sjj1sk8gIyh6cUocGmH4L0UuhAJy+hJMRA4mgA4mFQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
globals@14.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oahGvuMGQlPw/ivIYBjVSrWAfWLBeku5tpPE2fOPLi+WHffIWbuh2tCjhyQhTBPMf5E9jDEH4FOmTYgYwbKwtQ==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
globals@15.8.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VZAJ4cewHTExBWDHR6yptdIBlx9YSSZuwojj9Nt5mBRXQzrKakDsVKQ1J63sklLvzAJm0X5+RpO4i3Y2hcOnFw==}
engines: {node: '>=18'}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
globalthis@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sFdI5LyBiNTHjRd7cGPWapiHWMOXKyuBNX/cWJ3NfzrZQVa8GI/8cofCl74AOVqq9W5kNmguTIzJ/1s2gyI9wA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
globby@13.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Y1zNGV+pzQdh7H39l9zgB4PJqjRNqydvdYCDG4HFXM4XuvSaQQlEc91IU1yALL8gUTDomgBAfz3XJdmUS+oo0w==}
engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
gopd@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-d65bNlIadxvpb/A2abVdlqKqV563juRnZ1Wtk6s1sIR8uNsXR70xqIzVqxVf1eTqDunwT2MkczEeaezCKTZhwA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
got@11.8.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6tfZ91bOr7bOXnK7PRDCGBLa1H4U080YHNaAQ2KsMGlLEzRbk44nsZF2E1IeRc3vtJHPVbKCYgdFbaGO2ljd8g==}
engines: {node: '>=10.19.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
graceful-fs@4.2.11:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RbJ5/jmFcNNCcDV5o9eTnBLJ/HszWV0P73bc+Ff4nS/rJj+YaS6IGyiOL0VoBYX+l1Wrl3k63h/KrH+nhJ0XvQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
graphemer@1.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EtKwoO6kxCL9WO5xipiHTZlSzBm7WLT627TqC/uVRd0HKmq8NXyebnNYxDoBi7wt8eTWrUrKXCOVaFq9x1kgag==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
gray-matter@4.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5v6yZd4JK3eMI3FqqCouswVqwugaA9r4dNZB1wwcmrD02QkV5H0y7XBQW8QwQqEaZY1pM9aqORSORhJRdNK44Q==}
engines: {node: '>=6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
har-schema@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Oqluz6zhGX8cyRaTQlFMPw80bSJVG2x/cFb8ZPhUILGgHka9SsokCCOQgpveePerqidZOrT14ipqfJb7ILcW5Q==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
har-validator@5.1.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nmT2T0lljbxdQZfspsno9hgrG3Uir6Ks5afism62poxqBM6sDnMEuPmzTq8XN0OEwqKLLdh1jQI3qyE66Nzb3w==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: this library is no longer supported
has-bigints@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tSvCKtBr9lkF0Ex0aQiP9N+OpV4zi2r/Nee5VkRDbaqv35RLYMzbwQfFSZZH0kR+Rd6302UJZ2p/bJCEoR3VoQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
has-flag@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sKJf1+ceQBr4SMkvQnBDNDtf4TXpVhVGateu0t918bl30FnbE2m4vNLX+VWe/dpjlb+HugGYzW7uQXH98HPEYw==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
has-flag@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EykJT/Q1KjTWctppgIAgfSO0tKVuZUjhgMr17kqTumMl6Afv3EISleU7qZUzoXDFTAHTDC4NOoG/ZxU3EvlMPQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
has-property-descriptors@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-55JNKuIW+vq4Ke1BjOTjM2YctQIvCT7GFzHwmfZPGo5wnrgkid0YQtnAleFSqumZm4az3n2BS+erby5ipJdgrg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
has-proto@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SJ1amZAJUiZS+PhsVLf5tGydlaVB8EdFpaSO4gmiUKUOxk8qzn5AIy4ZeJUmh22znIdk/uMAUT2pl3FxzVUH+Q==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
has-symbols@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-l3LCuF6MgDNwTDKkdYGEihYjt5pRPbEg46rtlmnSPlUbgmB8LOIrKJbYYFBSbnPaJexMKtiPO8hmeRjRz2Td+A==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
has-tostringtag@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NqADB8VjPFLM2V0VvHUewwwsw0ZWBaIdgo+ieHtK3hasLz4qeCRjYcqfB6AQrBggRKppKF8L52/VqdVsO47Dlw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hash-sum@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WdZTbAByD+pHfl/g9QSsBIIwy8IT+EsPiKDs0KNX+zSHhdDLFKdZu0BQHljvO+0QI/BasbMSUa8wYNCZTvhslg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hash-wasm@4.11.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HVusNXlVqHe0fzIzdQOGolnFN6mX/fqcrSAOcTBXdvzrXVHwTz11vXeKRmkR5gTuwVpvHZEIyKoePDvuAR+XwQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasown@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0hJU9SCPvmMzIBdZFqNPXWa6dqh7WdH0cII9y+CyS8rG3nL48Bclra9HmKhVVUHyPWNH5Y7xDwAB7bfgSjkUMQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
he@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-F/1DnUGPopORZi0ni+CvrCgHQ5FyEAHRLSApuYWMmrbSwoN2Mn/7k+Gl38gJnR7yyDZk6WLXwiGod1JOWNDKGw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
header-case@2.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-H/vuk5TEEVZwrR0lp2zed9OCo1uAILMlx0JEMgC26rzyJJ3N1v6XkwHHXJQdR2doSjcGPM6OKPYoJgf0plJ11Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
hermes-estree@0.20.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SQpZK4BzR48kuOg0v4pb3EAGNclzIlqMj3Opu/mu7bbAoFw6oig6cEt/RAi0zTFW/iW6Iz9X9ggGuZTAZ/yZHg==}
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
hermes-parser@0.20.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BL5P83cwCogI8D7rrDCgsFY0tdYUtmFP9XaXtl2IQjC+2Xo+4okjfXintlTxcIwl4qeGddEl28Z11kbVIw0aNA==}
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
histoire@0.17.17:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DAwY4sgIoP7NGE5ldaws2d3RWz4OOQcwhS8elRMiA2euqzLvDU2IXm+ZjeDDFVtGkvmQNQyfZBDKLCLHfRkSUg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
peerDependencies:
vite: ^2.9.0 || ^3.0.0 || ^4.0.0 || ^5.0.0
hoist-non-react-statics@3.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/gGivxi8JPKWNm/W0jSmzcMPpfpPLc3dY/6GxhX2hQ9iGj3aDfklV4ET7NjKpSinLpJ5vafa9iiGIEZg10SfBw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hookable@5.5.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Yc+BQe8SvoXH1643Qez1zqLRmbA5rCL+sSmk6TVos0LWVfNIB7PGncdlId77WzLGSIB5KaWgTaNTs2lNVEI6VQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hosted-git-info@2.8.9:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mxIDAb9Lsm6DoOJ7xH+5+X4y1LU/4Hi50L9C5sIswK3JzULS4bwk1FvjdBgvYR4bzT4tuUQiC15FE2f5HbLvYw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hosted-git-info@4.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kyCuEOWjJqZuDbRHzL8V93NzQhwIB71oFWSyzVo+KPZI+pnQPPxucdkrOZvkLRnrf5URsQM+IJ09Dw29cRALIA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
html-encoding-sniffer@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Y22oTqIU4uuPgEemfz7NDJz6OeKf12Lsu+QC+s3BVpda64lTiMYCyGwg5ki4vFxkMwQdeZDl2adZoqUgdFuTgQ==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
html-escaper@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-H2iMtd0I4Mt5eYiapRdIDjp+XzelXQ0tFE4JS7YFwFevXXMmOp9myNrUvCg0D6ws8iqkRPBfKHgbwig1SmlLfg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
html-tags@3.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ztqyC3kLto0e9WbNp0aeP+M3kTt+nbaIveGmUxAtZa+8iFgKLUOD4YKM5j+f3QD89bra7UeumolZHKuOXnTmeQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
htmlparser2@8.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GYdjWKDkbRLkZ5geuHs5NY1puJ+PXwP7+fHPRz06Eirsb9ugf6d8kkXav6ADhcODhFFPMIXyxkxSuMf3D6NCFA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
http-cache-semantics@4.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-er295DKPVsV82j5kw1Gjt+ADA/XYHsajl82cGNQG2eyoPkvgUhX+nDIyelzhIWbbsXP39EHcI6l5tYs2FYqYXQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
http-errors@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FtwrG/euBzaEjYeRqOgly7G0qviiXoJWnvEH2Z1plBdXgbyjv34pHTSb9zoeHMyDy33+DWy5Wt9Wo+TURtOYSQ==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
http-proxy-agent@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-n2hY8YdoRE1i7r6M0w9DIw5GgZN0G25P8zLCRQ8rjXtTU3vsNFBI/vWK/UIeE6g5MUUz6avwAPXmL6Fy9D/90w==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
http-proxy-agent@7.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-T1gkAiYYDWYx3V5Bmyu7HcfcvL7mUrTWiM6yOfa3PIphViJ/gFPbvidQ+veqSOHci/PxBcDabeUNCzpOODJZig==}
engines: {node: '>= 14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
http-signature@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CAbnr6Rz4CYQkLYUtSNXxQPUH2gK8f3iWexVlsnMeD+GjlsQ0Xsy1cOX+mN3dtxYomRy21CiOzU8Uhw6OwncEQ==}
engines: {node: '>=0.8', npm: '>=1.3.7'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
http2-wrapper@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-V+23sDMr12Wnz7iTcDeJr3O6AIxlnvT/bmaAAAP/Xda35C90p9599p0F1eHR/N1KILWSoWVAiOMFjBBXaXSMxg==}
engines: {node: '>=10.19.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
https-proxy-agent@5.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dFcAjpTQFgoLMzC2VwU+C/CbS7uRL0lWmxDITmqm7C+7F0Odmj6s9l6alZc6AELXhrnggM2CeWSXHGOdX2YtwA==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
https-proxy-agent@7.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1e4Wqeblerz+tMKPIq2EMGiiWW1dIjZOksyHWSUm1rmuvw/how9hBHZ38lAGj5ID4Ik6EdkOw7NmWPy6LAwalw==}
engines: {node: '>= 14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
human-signals@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AXcZb6vzzrFAUE61HnN4mpLqd/cSIwNQjtNWR0euPm6y0iqx3G4gOXaIDdtdDwZmhwe82LA6+zinmW4UBWVePQ==}
engines: {node: '>=16.17.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
iconv-corefoundation@1.1.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-T10qvkw0zz4wnm560lOEg0PovVqUXuOFhhHAkixw8/sycy7TJt7v/RrkEKEQnAw2viPSJu6iAkErxnzR0g8PpQ==}
engines: {node: ^8.11.2 || >=10}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
os: [darwin]
iconv-lite@0.4.24:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-v3MXnZAcvnywkTUEZomIActle7RXXeedOR31wwl7VlyoXO4Qi9arvSenNQWne1TcRwhCL1HwLI21bEqdpj8/rA==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
iconv-lite@0.6.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4fCk79wshMdzMp2rH06qWrJE4iolqLhCUH+OiuIgU++RB0+94NlDL81atO7GX55uUKueo0txHNtvEyI6D7WdMw==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
idb-keyval@6.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8Sb3veuYCyrZL+VBt9LJfZjLUPWVvqn8tG28VqYNFCo43KHcKuq+b4EiXGeuaLAQWL2YmyDgMp2aSpH9JHsEQg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ieee754@1.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dcyqhDvX1C46lXZcVqCpK+FtMRQVdIMN6/Df5js2zouUsqG7I6sFxitIC+7KYK29KdXOLHdu9zL4sFnoVQnqaA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ignore@5.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5Fytz/IraMjqpwfd34ke28PTVMjZjJG2MPn5t7OE4eUCUNf8BAa7b5WUS9/Qvr6mwOQS7Mk6vdsMno5he+T8Xw==}
engines: {node: '>= 4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
image-size@0.5.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6TDAlDPZxUFCv+fuOkIoXT/V/f3Qbq8e37p+YOiYrUv3v9cc3/6x78VdfPgFVaB9dZYeLUfKgHRebpkm/oP2VQ==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
immediate@3.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XXOFtyqDjNDAQxVfYxuF7g9Il/IbWmmlQg2MYKOH8ExIT1qg6xc4zyS3HaEEATgs1btfzxq15ciUiY7gjSXRGQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
immediate@3.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HR7EVodfFUdQCTIeySw+WDRFJlPcLOJbXfwwZ7Oom6tjsvZ3bOkCDJHehQC3nxJrv7+f9XecwazynjU8e4Vw3Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
import-fresh@3.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-veYYhQa+D1QBKznvhUHxb8faxlrwUnxseDAbAp457E0wLNio2bOSKnjYDhMj+YiAq61xrMGhQk9iXVk5FzgQMw==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
imurmurhash@0.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JmXMZ6wuvDmLiHEml9ykzqO6lwFbof0GG4IkcGaENdCRDDmMVnny7s5HsIgHCbaq0w2MyPhDqkhTUgS2LU2PHA==}
engines: {node: '>=0.8.19'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
indefinitely-typed@1.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-giaI0hCj+wWZIZZLsmWHI+LrM4Hwc+rEZ/VrgCafKePcnE42fLnQTFt4xspqLin8fCjI5WnQr2fep/0EFqjaxw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
inflight@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-k92I/b08q4wvFscXCLvqfsHCrjrF7yiXsQuIVvVE7N82W3+aqpzuUdBbfhWcy/FZR3/4IgflMgKLOsvPDrGCJA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
inherits@2.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-k/vGaX4/Yla3WzyMCvTQOXYeIHvqOKtnqBduzTHpzpQZzAskKMhZ2K+EnBiSM9zGSoIFeMpXKxa4dYeZIQqewQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ini@1.3.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JV/yugV2uzW5iMRSiZAyDtQd+nxtUnjeLt0acNdw98kKLrvuRVyB80tsREOE7yvGVgalhZ6RNXCmEHkUKBKxew==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
MFA (#10875) * Draft checkbox component * Fixes in Setup Page * Invite Users * Add usergroup setup after subscription * Fix comments * Refetch Interval + Feature Toggles * Fix lint * Address issues * Fix Dialog * Assign users to the user group * Use transitions to navigate between steps * Small fixes * Improve styling for scrollbars * Fix typescript * OTP input * Fix setup logic * Show Setup dialog only for admins * Add otp * OTP input * 2FA settings section * Small improvements * Fixes * Small fixes * Remove w-full * TOTP at login * Fixes in 2FA * Fixes in types * Fix totp * Merge fixes * Merge fixes x2 * Merge fixes x2 * Fix types * Fix types * Fix cancel button * Fix reset button * Fix types * Fix prettier * Fix prettier * Fix lint * Fix lint * Fix control * Address prettier * Fix MFA mock * Fix sign in message * Fix tests * Address CR * Fix types
2024-09-13 16:00:31 +03:00
input-otp@1.2.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-md6rhmD+zmMnUh5crQNSQxq3keBRYvE3odbr4Qb9g2NWzQv9azi+t1a3X4TBTbh98fsGHgEEJlzbe1q860uGCA==}
MFA (#10875) * Draft checkbox component * Fixes in Setup Page * Invite Users * Add usergroup setup after subscription * Fix comments * Refetch Interval + Feature Toggles * Fix lint * Address issues * Fix Dialog * Assign users to the user group * Use transitions to navigate between steps * Small fixes * Improve styling for scrollbars * Fix typescript * OTP input * Fix setup logic * Show Setup dialog only for admins * Add otp * OTP input * 2FA settings section * Small improvements * Fixes * Small fixes * Remove w-full * TOTP at login * Fixes in 2FA * Fixes in types * Fix totp * Merge fixes * Merge fixes x2 * Merge fixes x2 * Fix types * Fix types * Fix cancel button * Fix reset button * Fix types * Fix prettier * Fix prettier * Fix lint * Fix lint * Fix control * Address prettier * Fix MFA mock * Fix sign in message * Fix tests * Address CR * Fix types
2024-09-13 16:00:31 +03:00
peerDependencies:
react: ^16.8 || ^17.0 || ^18.0
react-dom: ^16.8 || ^17.0 || ^18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
install@0.13.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zDml/jzr2PKU9I8J/xyZBQn8rPCAY//UOYNmR01XwNwyfhEWObo2SWfSl1+0tm1u6PhxLwDnfsT/6jB7OUxqFA==}
engines: {node: '>= 0.10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
internal-slot@1.0.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NGnrKwXzSms2qUUih/ILZ5JBqNTSa1+ZmP6flaIp6KmSElgE9qdndzS3cqjrDovwFdmwsGsLdeFgB6suw+1e9g==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
internmap@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5Hh7Y1wQbvY5ooGgPbDaL5iYLAPzMTUrjMulskHLH6wnv/A+1q5rgEaiuqEjB+oxGXIVZs1FF+R/KPN3ZSQYYg==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
intl-messageformat@10.5.14:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-IjC6sI0X7YRjjyVH9aUgdftcmZK7WXdHeil4KwbjDnRWjnVitKpAx3rr6t6di1joFp5188VqKcobOPA6mCLG/w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ip-regex@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HjpCHTuxbR/6jWJroc/VN+npo5j0T4Vv2TAI5qdEHQx7hsL767MeccGFSsLtF694EiZKTSEqgoeU6DtGFCcuqQ==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-array-buffer@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wcjaerHw0ydZwfhiKbXJWLDY8A7yV7KhjQOpb83hGgGfId/aQa4TOvwyzn2PuswW2gPCYEL/nEAiSVpdOj1lXw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-arrayish@0.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zz06S8t0ozoDXMG+ube26zeCTNXcKIPJZJi8hBrF4idCLms4CG9QtK7qBl1boi5ODzFpjswb5JPmHCbMpjaYzg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-arrayish@0.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eVRqCvVlZbuw3GrM63ovNSNAeA1K16kaR/LRY/92w0zxQ5/1YzwblUX652i4Xs9RwAGjW9d9y6X88t8OaAJfWQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-async-function@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Y1JXKrfykRJGdlDwdKlLpLyMIiWqWvuSd17TvZk68PLAOGOoF4Xyav1z0Xhoi+gCYjZVeC5SI+hYFOfvXmGRCA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-bigint@1.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zB9CruMamjym81i2JZ3UMn54PKGsQzsJeo6xvN3HJJ4CAsQNB6iRutp2To77OfCNuoxspsIhzaPoO1zyCEhFOg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-binary-path@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZMERYes6pDydyuGidse7OsHxtbI7WVeUEozgR/g7rd0xUimYNlvZRE/K2MgZTjWy725IfelLeVcEM97mmtRGXw==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-boolean-object@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gDYaKHJmnj4aWxyj6YHyXVpdQawtVLHU5cb+eztPGczf6cjuTdwve5ZIEfgXqH4e57An1D1AKf8CZ3kYrQRqYA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-callable@1.2.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1BC0BVFhS/p0qtw6enp8e+8OD0UrK0oFLztSjNzhcKA3WDuJxxAPXzPuPtKkjEY9UUoEWlX/8fgKeu2S8i9JTA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-ci@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZYvCgrefwqoQ6yTyYUbQu64HsITZ3NfKX1lzaEYdkTDcfKzzCI/wthRRYKkdjHKFVgNiXKAKm65Zo1pk2as/QQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
is-core-module@2.13.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hHrIjvZsftOsvKSn2TRYl63zvxsgE0K+0mYMoH6gD4omR5IWB2KynivBQczo3+wF1cCkjzvptnI9Q0sPU66ilw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-data-view@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AHkaJrsUVW6wq6JS8y3JnM/GJF/9cf+k20+iDzlSaJrinEo5+7vRiteOSwBhHRiAyQATN1AmY4hwzxJKPmYf+w==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-date-object@1.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9YQaSxsAiSwcvS33MBk3wTCVnWK+HhF8VZR2jRxehM16QcVOdHqPn4VPHmRK4lSr38n9JriurInLcP90xsYNfQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-docker@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eljcgEDlEns/7AXFosB5K/2nCM4P7FQPkGc/DWLy5rmFEWvZayGrik1d9/QIY5nJ4f9YsVvBkA6kJpHn9rISdQ==}
engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
is-extendable@0.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5BMULNob1vgFX6EjQw5izWDxrecWK9AM72rugNr0TFldMOi0fj6Jk+zeKIt0xGj4cEfQIJth4w3OKWOJ4f+AFw==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-extglob@2.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SbKbANkN603Vi4jEZv49LeVJMn4yGwsbzZworEoyEiutsN3nJYdbO36zfhGJ6QEDpOZIFkDtnq5JRxmvl3jsoQ==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-finalizationregistry@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0by5vtUJs8iFQb5TYUHHPudOR+qXYIMKtiUzvLIZITZUjknFmziyBJuLhVRc+Ds0dREFlskDNJKYIdIzu/9pfw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-fullwidth-code-point@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zymm5+u+sCsSWyD9qNaejV3DFvhCKclKdizYaJUuHA83RLjb7nSuGnddCHGv0hk+KY7BMAlsWeK4Ueg6EV6XQg==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-function@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-lw7DUp0aWXYg+CBCN+JKkcE0Q2RayZnSvnZBlwgxHBQhqt5pZNVy4Ri7H9GmmXkdu7LUthszM+Tor1u/2iBcpQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-generator-function@1.0.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jsEjy9l3yiXEQ+PsXdmBwEPcOxaXWLspKdplFUVI9vq1iZgIekeC0L167qeu86czQaxed3q/Uzuw0swL0irL8A==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-glob@4.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xelSayHH36ZgE7ZWhli7pW34hNbNl8Ojv5KVmkJD4hBdD3th8Tfk9vYasLM+mXWOZhFkgZfxhLSnrwRr4elSSg==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-inside-container@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KIYLCCJghfHZxqjYBE7rEy0OBuTd5xCHS7tHVgvCLkx7StIoaxwNW3hCALgEUjFfeRk+MG/Qxmp/vtETEF3tRA==}
engines: {node: '>=14.16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
is-map@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1Qed0/Hr2m+YqxnM09CjA2d/i6YZNfF6R2oRAOj36eUdS6qIV/huPJNSEpKbupewFs+ZsJlxsjjPbc0/afW6Lw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-negative-zero@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5KoIu2Ngpyek75jXodFvnafB6DJgr3u8uuK0LEZJjrU19DrMD3EVERaR8sjz8CCGgpZvxPl9SuE1GMVPFHx1mw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-network-error@1.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tUdRRAnhT+OtCZR/LxZelH/C7QtjtFrTu5tXCA8pl55eTUElUHT+GPYV8MBMBvea/j+NxQqVt3LbWMRir7Gx9g==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-number-object@1.0.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-k1U0IRzLMo7ZlYIfzRu23Oh6MiIFasgpb9X76eqfFZAqwH44UI4KTBvBYIZ1dSL9ZzChTB9ShHfLkR4pdW5krQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-number@7.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-41Cifkg6e8TylSpdtTpeLVMqvSBEVzTttHvERD741+pnZ8ANv0004MRL43QKPDlK9cGvNp6NZWZUBlbGXYxxng==}
engines: {node: '>=0.12.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-potential-custom-element-name@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bCYeRA2rVibKZd+s2625gGnGF/t7DSqDs4dP7CrLA1m7jKWz6pps0LpYLJN8Q64HtmPKJ1hrN3nzPNKFEKOUiQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-regex@1.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kvRdxDsxZjhzUX07ZnLydzS1TU/TJlTUHHY4YLL87e37oUA49DfkLqgy+VjFocowy29cKvcSiu+kIv728jTTVg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-set@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iPAjerrse27/ygGLxw+EBR9agv9Y6uLeYVJMu+QNCoouJ1/1ri0mGrcWpfCqFZuzzx3WjtwxG098X+n4OuRkPg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-shared-array-buffer@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nA2hv5XIhLR3uVzDDfCIknerhx8XUKnstuOERPNNIinXG7v9u+ohXF67vxm4TPTEPU6lm61ZkwP3c9PCB97rhg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-stream@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-LnQR4bZ9IADDRSkvpqMGvt/tEJWclzklNgSw48V5EAaAeDd6qGvN8ei6k5p0tvxSR171VmGyHuTiAOfxAbr8kA==}
engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-string@1.0.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tE2UXzivje6ofPW7l23cjDOMa09gb7xlAqG6jG5ej6uPV32TlWP3NKPigtaGeHNu9fohccRYvIiZMfOOnOYUtg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-symbol@1.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-C/CPBqKWnvdcxqIARxyOh4v1UUEOCHpgDa0WYgpKDFMszcrPcffg5uhwSgPCLD2WWxmq6isisz87tzT01tuGhg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-typed-array@1.1.13:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-uZ25/bUAlUY5fR4OKT4rZQEBrzQWYV9ZJYGGsUmEJ6thodVJ1HX64ePQ6Z0qPWP+m+Uq6e9UugrE38jeYsDSMw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-typedarray@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cyA56iCMHAh5CdzjJIa4aohJyeO1YbwLi3Jc35MmRU6poroFjIGZzUzupGiRPOjgHg9TLu43xbpwXk523fMxKA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-url@1.2.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ITvGim8FhRiYe4IQ5uHSkj7pVaPDrCTkNd3yq3cV7iZAcJdHTUMPMEHcqSOy9xZ9qFenQCvi+2wjH9a1nXqHww==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-weakmap@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-K5pXYOm9wqY1RgjpL3YTkF39tni1XajUIkawTLUo9EZEVUFga5gSQJF8nNS7ZwJQ02y+1YCNYcMh+HIf1ZqE+w==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-weakref@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qctsuLZmIQ0+vSSMfoVvyFe2+GSEvnmZ2ezTup1SBse9+twCCeial6EEi3Nc2KFcf6+qz2FBPnjXsk8xhKSaPQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-weakset@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-LvIm3/KWzS9oRFHugab7d+M/GcBXuXX5xZkzPmN+NxihdQlZUQ4dWuSV1xR/sq6upL1TJEDrfBgRepHFdBtSNQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-what@4.1.16:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZhMwEosbFJkA0YhFnNDgTM4ZxDRsS6HqTo7qsZM08fehyRYIYa0yHu5R6mgo1n/8MgaPBXiPimPD77baVFYg+A==}
engines: {node: '>=12.13'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-wsl@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UcVfVfaK4Sc4m7X3dUSoHoozQGBEFeDC+zVo06t98xe8CzHSZZBekNXH+tu0NalHolcJ/QAGqS46Hef7QXBIMw==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isarray@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VLghIWNM6ELQzo7zwmcg0NmTVyWKYjvIeM83yjp0wRDTmUnrM678fQbcKBo6n2CJEF0szoG//ytg+TKla89ALQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isarray@2.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xHjhDr3cNBK0BzdUJSPXZntQUx/mwMS5Rw4A7lPJ90XGAO6ISP/ePDNuo0vhqOZU+UD5JoodwCAAoZQd3FeAKw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isbinaryfile@4.0.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iHrqe5shvBUcFbmZq9zOQHBoeOhZJu6RQGrDpBgenUm/Am+F3JM2MgQj+rK3Z601fzrL5gLZWtAPH2OBaSVcyw==}
engines: {node: '>= 8.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isbinaryfile@5.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GvcjojwonMjWbTkfMpnVHVqXW/wKMYDfEpY94/8zy8HFMOqb/VL6oeONq9v87q4ttVlaTLnGXnJD4B5B1OTGIg==}
engines: {node: '>= 18.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isexe@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RHxMLp9lnKHGHRng9QFhRCMbYAcVpn69smSGcq3f36xjgVVWThj4qqLbTLlq7Ssj8B+fIQ1EuCEGI2lKsyQeIw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isomorphic-fetch@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qvUtwJ3j6qwsF3jLxkZ72qCgjMysPzDfeV240JHiGZsANBYd+EEuu35v7dfrJ9Up0Ak07D7GGSkGhCHTqg/5wA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isomorphic-unfetch@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-geDJjpoZ8N0kWexiwkX8F9NkTsXhetLPVbZFQ+JTW239QNOwvB0gniuR1Wc6f0AMTn7/mFGyXvHTifrCp/GH8Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isomorphic-ws@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-muId7Zzn9ywDsyXgTIafTry2sV3nySZeUDe6YedVd1Hvuuep5AsIlqK+XefWpYTyJG5e503F2xIuT2lcU6rCSw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws: ^8.18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isomorphic.js@0.2.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PIeMbHqMt4DnUP3MA/Flc0HElYjMXArsw1qwJZcm9sqR8mq3l8NYizFMty0pWwE/tzIGH3EKK5+jes5mAr85yw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isstream@0.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Yljz7ffyPbrLpLngrMtZ7NduUgVvi6wG9RJ9IUcyCd59YQ911PBJphODUcbOVbqYfxe1wuYf/LJ8PauMRwsM/g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
istanbul-lib-coverage@3.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-O8dpsF+r0WV/8MNRKfnmrtCWhuKjxrq2w+jpzBL5UZKTi2LeVWnWOmWRxFlesJONmc+wLAGvKQZEOanko0LFTg==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
istanbul-lib-report@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GCfE1mtsHGOELCU8e/Z7YWzpmybrx/+dSTfLrvY8qRmaY6zXTKWn6WQIjaAFw069icm6GVMNkgu0NzI4iPZUNw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
istanbul-lib-source-maps@5.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gKf4eJ8bHmSX/ljiOCpnd8vtmHTwG71uugm0kXYd5aqFCl6z8cj8k7QduXSwU6QOst6LCdSXTlaoc8W4554crQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
istanbul-reports@3.1.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BewmUXImeuRk2YY0PVbxgKAysvhRPUQE0h5QRM++nVWyubKGV0l8qQ5op8+B2DOmwSe63Jivj0BjkPQVf8fP5g==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
iterator.prototype@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DR33HMMr8EzwuRL8Y9D3u2BMj8+RqSE850jfGu59kS7tbmPLzGkZmVSfyCFSDxuZiEY6Rzt3T2NA/qU+NwVj1w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jackspeak@3.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JVYhQnN59LVPFCEcVa2C3CrEKYacvjRfqIQl+h8oi91aLYQVWRYbxjPcv1bUiUy/kLmQaANrYfNMCO3kuEDHfw==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
jackspeak@4.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cub8rahkh0Q/bw1+GxP7aeSe29hHHn2V4m29nnDlvCdlgU+3UGxkZp7Z53jLUdpX3jdTO0nJZUDl3xvbWc2Xog==}
engines: {node: 20 || >=22}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jake@10.9.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-61btcOHNnLnsOdtLgA5efqQWjnSi/vow5HbI7HMdKKWqvrKR1bLK3BPlJn9gcSaP2ewuamUSMB5XEy76KUIS2w==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
jimp@0.2.28:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9HT7DA279xkTlry2oG30s6AtOUglNiY2UdyYpj0yNI4/NBv8PmdNC0gcldgMU4HqvbUlrM3+v+6GaHnTkH23JQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jiti@1.21.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2yTgeWTWzMWkHu6Jp9NKgePDaYHbntiwvYuuJLbbN9vl7DC9DvXKOB2BC3ZZ92D3cvV/aflH0osDfwpHepQ53w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
jpeg-js@0.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CiRVjMKBUp6VYtGwzRjrdnro41yMwKGOWdP9ATXqmixdz2n7KHNwdqthTYSSbOKj/Ha79Gct1sA8ZQpse55TYA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jpeg-js@0.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Ni9PffhJtYtdD7VwxH6V2MnievekGfUefosGCHadog0/jAevRu6HPjYeMHbUemn0IPE8d4wGa8UsOGsX+iKy2g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
js-beautify@1.15.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ESjNzSlt/sWE8sciZH8kBF8BPlwXPwhR6pWKAw8bw4Bwj+iZcnKW6ONWUutJ7eObuBZQpiIb8S7OYspWrKt7rA==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
js-cookie@2.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HvdH2LzI/EAZcUwA8+0nKNtWHqS+ZmijLA30RwZA0bo7ToCckjK5MkGhjED9KoRcXO6BaGI3I9UIzSA1FKFPOQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
js-cookie@3.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cEiJEAEoIbWfCZYKWhVwFuvPX1gETRYPw6LlaTKoxD3s2AkXzkCjnp6h0V77ozyqj0jakteJ4YqDJT830+lVGw==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
js-message@1.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hTqHqrm7jrZ+iN93QsKcNOTSgX3F+2NSgdnF+xvf8FfhC2MPqYRzzgXQ1LlhfyIzPTS6hL6Zea0/gIb6hktkHw==}
engines: {node: '>=0.6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
js-queue@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SW0rTTG+TBPVD1Kp6HtnOr9kX3//EWA6qMlP2Y/WxbKsSNCBuJbWv3EDB5noKJBEkHYi2mDY+xqMn4Y0QHyjyg==}
engines: {node: '>=1.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
js-tokens@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RdJUflcE3cUzKiMqQgsCu06FPu9UdIJO0beYbPhHN4k6apgJtifcoCtT9bcxOpYBtpD2kCM6Sbzg4CausW/PKQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
js-tokens@9.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WriZw1luRMlmV3LGJaR6QOJjWwgLUTf89OwT2lUOyjX2dJGBwgmIkbcz+7WFZjrZM635JOIR517++e/67CP9dQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
js-yaml@3.14.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-okMH7OXXJ7YrN9Ok3/SXrnu4iX9yOk+25nqX4imS2npuvTYDmo/QEZoqwZkYaIDk3jVvBOTOIEgEhaLOynBS9g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
js-yaml@4.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wpxZs9NoxZaJESJGIZTyDEaYpl0FKSA+FB9aJiyemKhMwkxQg63h4T1KJgUGHpTqPDNRcmmYLugrRjJlBtWvRA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
jsbn@0.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UVU9dibq2JcFWxQPA6KCqj5O42VOmAY3zQUfEKxU0KpTGXwNoCjkX1e13eHNvw/xPynt6pU0rZ1htjWTNTSXsg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
jsdoc-type-pratt-parser@4.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Hicd6JK5Njt2QB6XYFS7ok9e37O8AYk3jTcppG4YVQnYjOemymvTcmc7OWsmq/Qqj5TdRFO5/x/tIPmBeRtGHg==}
engines: {node: '>=12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsdom@24.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6gpM7pRXCwIOKxX47cgOyvyQDN/Eh0f1MeKySBV2xGdKtqJBLj8P25eY3EVCWo2mglDDzozR2r2MW4T+JiNUZA==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
canvas: ^2.11.2
peerDependenciesMeta:
canvas:
optional: true
jsesc@2.5.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-OYu7XEzjkCQ3C5Ps3QIZsQfNpqoJyZZA99wd9aWd05NCtC5pWOkShK2mkL6HXQR6/Cy2lbNdPlZBpuQHXE63gA==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
json-buffer@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4bV5BfR2mqfQTJm+V5tPPdf+ZpuhiIvTuAB5g8kcrXOZpTT/QwwVRWBywX1ozr6lEuPdbHxwaJlm9G6mI2sfSQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
json-parse-better-errors@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mrqyZKfX5EhL7hvqcV6WG1yYjnjeuYDzDhhcAAUrq8Po85NBQBJP+ZDUT75qZQ98IkUoBqdkExkukOU7Ts2wrw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
json-schema-faker@0.5.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-u/cFC26/GDxh2vPiAC8B8xVvpXAW+QYtG2mijEbKrimCk8IHtiwQBjCE8TwvowdhALWq9IcdIWZ+/8ocXvdL3Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
json-schema-ref-parser@6.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pXe9H1m6IgIpXmE5JSb8epilNTGsmTb2iPohAXpOdhqGFbQjNeHHsZxU+C8w6T81GZxSPFLeUoqDJmzxx5IGuw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: Please switch to @apidevtools/json-schema-ref-parser
json-schema-traverse@0.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xbbCH5dCYU5T8LcEhhuh7HJ88HXuW3qsI3Y0zOZFKfZEHcpWiHU/Jxzk629Brsab/mMiHQti9wMP+845RPe3Vg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
json-schema-traverse@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NM8/P9n3XjXhIZn1lLhkFaACTOURQXjWhV4BA/RnOv8xvgqtqpAX9IO4mRQxSx1Rlo4tqzeqb0sOlruaOy3dug==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
json-schema@0.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-es94M3nTIfsEPisRafak+HDLfHXnKBhV3vU5eqPcS3flIWqcxJWgXHXiey3YrpaNsanY5ei1VoYEbOzijuq9BA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
json-stable-stringify-without-jsonify@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Bdboy+l7tA3OGW6FjyFHWkP5LuByj1Tk33Ljyq0axyzdk9//JSi2u3fP1QSmd1KNwq6VOKYGlAu87CisVir6Pw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
json-stringify-safe@5.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZClg6AaYvamvYEE82d3Iyd3vSSIjQ+odgjaTzRuO3s7toCdFKczob2i0zCh7JE8kWn17yvAWhUVxvqGwUalsRA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
json5@2.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XmOWe7eyHYH14cLdVPoyg+GOH3rYX++KpzrylJwSW98t3Nk+U8XOl8FWKOgwtzdb8lXGf6zYwDUzeHMWfxasyg==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
jsonfile@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-m6F1R3z8jjlf2imQHS2Qez5sjKWQzbuuhuJ/FKYFRZvPE3PuHcSMVZzfsLhGVOkfd20obL5SWEBew5ShlquNxg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsonfile@6.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5dgndWOriYSm5cnYaJNhalLNDKOqFwyDB/rr1E9ZsGciGvKPs8R2xYGCacuf3z6K1YKDz182fd+fY3cn3pMqXQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsonpath-plus@7.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zBfiUPM5nD0YZSBT/o/fbCUlCcepMIdP0CJZxM1+KgA4f2T206f6VAg9e7mX35+KlMaIc5qXW34f3BnwJ3w+RA==}
engines: {node: '>=12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsprim@1.4.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-P2bSOMAc/ciLz6DzgjVlGJP9+BrJWu5UDGK70C2iweC5QBIeFf0ZXRvGjEj2uYgrY2MkAAhsSWHDWlFtEroZWw==}
engines: {node: '>=0.6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsx-ast-utils@3.3.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZZow9HBI5O6EPgSJLUb8n2NKgmVWTwCvHGwFuJlMjvLFqlGG6pjirPhtdsseaLZjSibD8eegzmYpUZwoIlj2cQ==}
engines: {node: '>=4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
keyv@4.5.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oxVHkHR/EJf2CNXnWxRLW6mg7JyCCUcG0DtEGmL2ctUo1PNTin1PUil+r/+4r5MpVgC/fn1kjsx7mjSujKqIpw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
kind-of@6.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dcS1ul+9tmeD95T+x28/ehLgd9mENa3LsvDTtzm3vyBEO7RPptvAD+t44WVXaUjTBRcrpFeFlC8WCruUR456hw==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
kolorist@1.8.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Y+60/zizpJ3HRH8DCss+q95yr6145JXZo46OTpFvDZWLfRCE4qChOyk1b26nMaNpfHHgxagk9dXT5OP0Tfe+dQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
launch-editor@2.8.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vJranOAJrI/llyWGRQqiDM+adrw+k83fvmmx3+nV47g3+36xM15jE+zyZ6Ffel02+xSvuM0b2GDRosXZkbb6wA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lazy-val@1.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0/BnGCCfyUMkBpeDgWihanIAF9JmZhHBgUhEqzvf+adhNGLoP6TaiI5oF8oyb3I45P+PcnrqihSf01M0l0G5+Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lazystream@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-b94GiNHQNy6JNTrt5w6zNyffMrNkXZb3KTkCZJb2V1xaEGCk093vkZ2jk3tpaeP33/OiXC+WvK9AxUebnf5nbw==}
engines: {node: '>= 0.6.3'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
level-codec@9.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UyIwNb1lJBChJnGfjmO0OR+ezh2iVu1Kas3nvBS/BzGnx79dv6g7unpKIDNPMhfdTEGoc7mC8uAu51XEtX+FHQ==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
level-concat-iterator@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-OTKKOqeav2QWcERMJR7IS9CUo1sHnke2C0gkSmcR7QuEtFNLLzHQAvnMw8ykvEcv0Qtkg0p7FOwP1v9e5Smdcw==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
level-errors@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UVprBJXite4gPS+3VznfgDSU8PTRuVX0NXwoWW50KLxd2yw4Y1t2JUR5In1itQnudZqRMT9DlAM3Q//9NCjCFw==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
level-iterator-stream@4.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZSthfEqzGSOMWoUGhTXdX9jv26d32XJuHz/5YnuHZzH6wldfWMOVwI9TBtKcya4BKTyTt3XVA0A3cF3q5CY30Q==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
level-js@5.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SnBIDo2pdO5VXh02ZmtAyPP6/+6YTJg2ibLtl9C34pWvmtMEmRTWpra+qO/hifkUtBTOtfx6S9vLDjBsBK4gRg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
level-packager@5.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HMwMaQPlTC1IlcwT3+swhqf/NUO+ZhXVz6TY1zZIIZlIR0YSn8GtAAWmIvKjNY16ZkEg/JcpAuQskxsXqC0yOQ==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
level-supports@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rXM7GYnW8gsl1vedTJIbzOrRv85c/2uCMpiiCzO2fndd06U/kUXEEU9evYn4zFggBOg36IsBW8LzqIpETwwQzg==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
level@6.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-psRSqJZCsC/irNhfHzrVZbmPYXDcEYhA5TVNwr+V92jF44rbf86hqGp8fiT702FyiArScYIlPSBTDUASCVNSpw==}
engines: {node: '>=8.6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
leveldown@5.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iB8O/7Db9lPaITU1aA2txU/cBEXAt4vWwKQRrrWuS6XDgbP4QZGj9BL2aNbwb002atoQ/lIotJkfyzz+ygQnUQ==}
engines: {node: '>=8.6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
levelup@4.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-94++VFO3qN95cM/d6eBXvd894oJE0w3cInq9USsyQzzoJxmiYzPAocNcuGCPGGjoXqDVJcr3C1jzt1TSjyaiLQ==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
levn@0.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+bT2uH4E5LGE7h/n3evcS/sQlJXCpIp6ym8OWJ5eV6+67Dsql/LaaT7qJBAt2rzfoa/5QBGBhxDix1dMt2kQKQ==}
engines: {node: '>= 0.8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical@0.16.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Skn45Qhriazq4fpAtwnAB11U//GKc4vjzx54xsV3TkDLDvWpbL4Z9TNRwRoN3g7w8AkWnqjeOSODKkrjgfRSrg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lib0@0.2.94:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hZ3p54jL4Wpu7IOg26uC7dnEWiMyNlUrb9KoG7+xYs45WkQwpVvKFndVq2+pqLYKe1u8Fp3+zAfZHVvTK34PvQ==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
lie@3.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RiNhHysUjhrDQntfYSfY4MU24coXXdEOgw9WGcKHNeEwffDYbF//u87M1EWaMGzuFoSbqW0C9C6lEEhDOAswfw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lightningcss-darwin-arm64@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-G4Dcvv85bs5NLENcu/s1f7ehzE3D5ThnlWSDwE190tWXRQCQaqwcuHe+MGSVI/slm0XrxnaayXY+cNl3cSricw==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm64]
os: [darwin]
lightningcss-darwin-x64@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dYWuCzzfqRueDSmto6YU5SoGHvZTMU1Em9xvhcdROpmtOQLorurUZz8+xFxZ51lCO2LnYbfdjZ/gCqWEkwixNg==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [darwin]
lightningcss-freebsd-x64@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hXoy2s9A3KVNAIoKz+Fp6bNeY+h9c3tkcx1J3+pS48CqAt+5bI/R/YY4hxGL57fWAIquRjGKW50arltD6iRt/w==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [freebsd]
lightningcss-linux-arm-gnueabihf@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tWyMgHFlHlp1e5iW3EpqvH5MvsgoN7ZkylBbG2R2LWxnvH3FuWCJOhtGcYx9Ks0Kv0eZOBud789odkYLhyf1ng==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm]
os: [linux]
lightningcss-linux-arm64-gnu@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Xjxsx286OT9/XSnVLIsFEDyDipqe4BcLeB4pXQ/FEA5+2uWCCuAEarUNQumRucnj7k6ftkAHUEph5r821KBccQ==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm64]
os: [linux]
lightningcss-linux-arm64-musl@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-IhxVFJoTW8wq6yLvxdPvyHv4NjzcpN1B7gjxrY3uaykQNXPHNIpChLB52+wfH+yS58zm1PL4LemUp8u9Cfp6Bw==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [arm64]
os: [linux]
lightningcss-linux-x64-gnu@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RXIaru79KrREPEd6WLXfKfIp4QzoppZvD3x7vuTKkDA64PwTzKJ2jaC43RZHRt8BmyIkRRlmywNhTRMbmkPYpA==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [linux]
lightningcss-linux-x64-musl@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TdcNqFsAENEEFr8fJWg0Y4fZ/nwuqTRsIr7W7t2wmDUlA8eSXVepeeONYcb+gtTj1RaXn/WgNLB45SFkz+XBZA==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [linux]
lightningcss-win32-x64-msvc@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9KZZkmmy9oGDSrnyHuxP6iMhbsgChUiu/NSgOx+U1I/wTngBStDf2i2aGRCHvFqj19HqqBEI4WuGVQBa2V6e0A==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cpu: [x64]
os: [win32]
lightningcss@1.25.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-V0RMVZzK1+rCHpymRv4URK2lNhIRyO8g7U7zOFwVAhJuat74HtkjIQpQRKNCwFEYkRGpafOpmXXLoaoBcyVtBg==}
engines: {node: '>= 12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lilconfig@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-utWOt/GHzuUxnLKxB6dk81RoOeoNeHgbrXiuGk4yyF5qlRz+iIVWu56E2fqGHFrXz0QNUhLB/8nKqvRH66JKGQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lilconfig@3.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eop+wDAvpItUys0FWkHIKeC9ybYrTGbU41U5K7+bttZZeohvnY7M9dZ5kB21GNWiFT2q1OoPTvncPCgSOVO5ow==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lines-and-columns@1.2.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7ylylesZQ/PV29jhEDl3Ufjo6ZX7gCqJr5F7PKrqc93v7fzSymt1BpwEU8nAUXs8qzzvqhbjhK5QZg6Mt/HkBg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
linkify-it@3.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ynTsyrFSdE5oZ/O9GEf00kPngmOfVwazR5GKDq6EYfhlpFug3J2zybX56a2PRRpc9P+FuSoGNAwjlbDs9jJBPQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
load-bmfont@1.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8UyQoYmdRDy81Brz6aLAUhfZLwr5zV0L3taTQ4hju7m6biuwiWiJXjPhBJxbUQJA8PrkvJ/7Enqmwk2sM14soA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
load-json-file@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Kx8hMakjX03tiGTLAIdJ+lL0htKnXjEZN6hk/tozf/WOuYGdZBJrZ+rCJRbVCugsjB3jMLn9746NsQIf5VjBMw==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
local-pkg@0.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ok6z3qlYyCDS4ZEU27HaU6x/xZa9Whf8jD4ptH5UZTQYZVYeb9bnZ3ojVhiJNLiXK1Hfc0GNbLXcmZ5plLDDBg==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
localforage@1.10.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-14/H1aX7hzBBmmh7sGPd+AOMkkIrHM3Z1PAyGgZigA1H1p5O5ANnMyWzvpAETtG68/dC4pC0ncy3+PPGzXZHPg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
locate-path@6.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iPZK6eYjbxRu3uB4/WZ3EsEIMJFMqAoopl3R+zuq0UjcAm/MO6KCweDgPfP3elTztoKP3KtnVHxTn2NHBSDVUw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash.debounce@4.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FT1yDzDYEoYWhnSGnpE/4Kj1fLZkDFyqRb7fNt6FdYOSxlUWAtp42Eh6Wb0rGIv/m9Bgo7x4GhQbm5Ys4SG5ow==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash.defaults@4.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qjxPLHd3r5DnsdGacqOMU6pb/avJzdh9tFX2ymgoZE27BmjXrNy/y4LoaiTeAb+O3gL8AfpJGtqfX/ae2leYYQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash.difference@4.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dS2j+W26TQ7taQBGN8Lbbq04ssV3emRw4NY58WErlTO29pIqS0HmoT5aJ9+TUQ1N3G+JOZSji4eugsWwGp9yPA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash.flatten@4.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-C5N2Z3DgnnKr0LOpv/hKCgKdb7ZZwafIrsesve6lmzvZIRZRGaZ/l6Q8+2W7NaT+ZwO3fFlSCzCzrDCFdJfZ4g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash.isplainobject@4.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oSXzaWypCMHkPC3NvBEaPHf0KsA5mvPrOPgQWDsbg8n7orZ290M0BmC/jgRZ4vcJ6DTAhjrsSYgdsW/F+MFOBA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash.merge@4.6.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0KpjqXRVvrYyCsX1swR/XTK0va6VQkQM6MNo7PqW77ByjAhoARA8EfrP1N4+KlKj8YS0ZUCtRT/YUuhyYDujIQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash.union@4.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-c4pB2CdGrGdjMKYLA+XiRDO7Y0PRQbm/Gzg8qMj+QH+pFVAoTp5sBpO0odL3FjoPCGjK96p6qsP+yQoiLoOBcw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash@4.17.21:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-v2kDEe57lecTulaDIuNTPy3Ry4gLGJ6Z1O3vE1krgXZNrsQ+LFTGHVxVjcXPs17LhbZVGedAJv8XZ1tvj5FvSg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
loose-envify@1.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-lyuxPGr/Wfhrlem2CL/UcnUc1zcqKAImBDzukY7Y5F/yQiNdko6+fRLevlw1HgMySw7f611UIY408EtxRSoK3Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
loupe@2.3.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zSMINGVYkdpYSOBmLi0D1Uo7JU9nVdQKrHxC8eYlV+9YKK9WePqAlL7lSlorG/U2Fw1w0hTBmaa/jrQ3UbPHtA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lower-case@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7fm3l3NAF9WfN6W3JOmf5drwpVqX78JtoGJ3A6W0a6ZnldM41w2fV5D490psKFTpMds8TJse/eHLFFsNHHjHgg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lowercase-keys@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tqNXrS78oMOE73NMxK4EMLQsQowWf8jKooH9g7xPavRT706R6bkQJ6DY2Te7QukaZsulxa30wQ7bk0pm4XiHmA==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lru-cache@10.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CQl19J/g+Hbjbv4Y3mFNNXFEL/5t/KCg8POCuUqd4rMKjGG+j1ybER83hxV58zL+dFI1PTkt3GNFSHRt+d8qEQ==}
engines: {node: 14 || >=16.14}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
lru-cache@11.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Qv32eSV1RSCfhY3fpPE2GNZ8jgM9X7rdAfemLWqTUxwiyIC4jJ6Sy0fZ8H+oLWevO6i4/bizg7c8d8i6bxrzbA==}
engines: {node: 20 || >=22}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lru-cache@5.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KpNARQA3Iwv+jTA0utUVVbrh+Jlrr1Fv0e56GGzAFOXN7dk/FviaDW8LHmK52DlcH4WP2n6gI8vN1aesBFgo9w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lru-cache@6.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Jo6dJ04CmSjuznwJSS3pUeWmd/H0ffTlkXXgwZi+eq1UCmqQwCh+eLsYOYCwY991i2Fah4h1BEMCx4qThGbsiA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ltgt@2.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AI2r85+4MquTw9ZYqabu4nMwy9Oftlfa/e/52t9IjtfG+mGBbTNdAoZ3RQKLHR6r0wQnwZnPIEh/Ya6XTWAKNA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
magic-string@0.30.11:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+Wri9p0QHMy+545hKww7YAu5NyzF8iomPL/RQazugQ9+Ez4Ic3mERMd8ZTX5rfK944j+560ZJi8iAwgak1Ac7A==}
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
magicast@0.3.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TyDF/Pn36bBji9rWKHlZe+PZb6Mx5V8IHCSxk7X4aljM4e/vyDvZZYwHewdVaqiA0nb3ghfHU/6AUpDxWoER2Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
make-dir@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hXdUTZYIVOt1Ex//jAQi+wTZZpUpwBj/0QsOzqegb3rGMMeJiSEu5xLHnYfBrRV4RH2+OCSOO95Is/7x1WJ4bw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
markdown-it-anchor@8.6.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FlCHFwNnutLgVTflOYHPW2pPcl2AACqVzExlkGQNsi4CJgqOHN7YTgDd4LuhgN1BFO3TS0vLAruV1Td6dwWPJA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/markdown-it': '*'
markdown-it: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
markdown-it-attrs@4.1.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-O7PDKZlN8RFMyDX13JnctQompwrrILuz2y43pW2GagcwpIIElkAdfeek+erHfxUOlXWPsjFeWmZ8ch1xtRLWpA==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
markdown-it: '>= 9.0.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
markdown-it-emoji@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zLftSaNrKuYl0kR5zm4gxXjHaOI3FAOEaloKmRA5hijmJZvSjmxcokOLlzycb/HXlUFWzXqpIEoyEMCE4i9MvQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
markdown-it@12.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TchMembfxfNVpHkbtriWltGWc+m3xszaRD0CZup7GFFhzIgQqxIfn3eGj1yZpfuflzPvfkt611B2Q/Bsk1YnGg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
marked@14.1.3:
resolution: {integrity: sha512-ZibJqTULGlt9g5k4VMARAktMAjXoVnnr+Y3aCqW1oDftcV4BA3UmrBifzXoZyenHRk75csiPu9iwsTj4VNBT0g==}
engines: {node: '>= 18'}
hasBin: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
matcher@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-OkeDaAZ/bQCxeFAozM55PKcKU0yJMPGifLwV4Qgjitu+5MoAfSQN4lsLJeXZ1b8w0x+/Emda6MZgXS1jvsapng==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mdurl@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/sKlQJCBYVY9Ers9hqzKou4H6V5UWc/M59TH2dvkt+84itfnq7uFOMLpOiOS4ujvHP4etln18fmIxA5R5fll0g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
media-typer@0.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dq+qelQ9akHpcOl/gUVRTxVIOkAJ1wR3QAvb4RsVjS8oVoFjDGTc679wJYmUmknUF5HwMLOgb5O+a3KxfWapPQ==}
engines: {node: '>= 0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
memorystream@0.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-S3UwM3yj5mtUSEfP41UZmt/0SCoVYUcU1rkXv+BQ5Ig8ndL4sPoJNBUJERafdPb5jjHJGuMgytgKvKIf58XNBw==}
engines: {node: '>= 0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
merge-stream@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-abv/qOcuPfk3URPfDzmZU1LKmuw8kT+0nIHvKrKgFrwifol/doWcdA4ZqsWQ8ENrFKkd67Mfpo/LovbIUsbt3w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
merge2@1.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8q7VEgMJW4J8tcfVPy8g09NcQwZdbwFEqhe/WZkoIzjn/3TGDwtOCYtXGxA3O8tPzpczCCDgv+P2P5y00ZJOOg==}
engines: {node: '>= 8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
micromatch@4.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DMy+ERcEW2q8Z2Po+WNXuw3c5YaUSFjAO5GsJqfEl7UjvtIuFKO6ZrKvcItdy98dwFI2N1tg3zNIdKaQT+aNdA==}
engines: {node: '>=8.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mime-db@1.52.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sPU4uV7dYlvtWJxwwxHD0PuihVNiE7TyAbQ5SWxDCB9mUYvOgroQOwYQQOKPJ8CIbE+1ETVlOoK1UC2nU3gYvg==}
engines: {node: '>= 0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mime-types@2.1.35:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZDY+bPm5zTTF+YpCrAU9nK0UgICYPT0QtT1NZWFv4s++TNkcgVaT0g6+4R2uI4MjQjzysHB1zxuWL50hzaeXiw==}
engines: {node: '>= 0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mime@1.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-x0Vn8spI+wuJ1O6S7gnbaQg8Pxh4NNHb7KSINmEWKiPE4RKOplvijn+NkmYmmRgP68mc70j2EbeTFRsrswaQeg==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
mime@2.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-USPkMeET31rOMiarsBNIHZKLGgvKc/LrjofAnBlOttf5ajRvqiRA8QsenbcooctK6d6Ts6aqZXBA+XbkKthiQg==}
engines: {node: '>=4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
mimic-fn@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vqiC06CuhBTUdZH+RYl8sFrL096vA45Ok5ISO6sE/Mr1jRbGH4Csnhi8f3wKVl7x8mO4Au7Ir9D3Oyv1VYMFJw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mimic-response@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-j5EctnkH7amfV/q5Hgmoal1g2QHFJRraOtmx0JpIqkxhBhI/lJSl1nMpQ45hVarwNETOoWEimndZ4QK0RHxuxQ==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mimic-response@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-z0yWI+4FDrrweS8Zmt4Ej5HdJmky15+L2e6Wgn3+iK5fWzb6T3fhNFq2+MeTRb064c6Wr4N/wv0DzQTjNzHNGQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
min-document@2.19.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9Wy1B3m3f66bPPmU5hdA4DR4PB2OfDU/+GS3yAB7IQozE3tqXaVv2zOjgla7MEGSRv95+ILmOuvhLkOK6wJtCQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
minimatch@10.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ethXTt3SGGR+95gudmqJ1eNhRO7eGEGIgYA9vnPatK4/etz2MEVDno5GMCibdMTuBMyElzIlgxMna3K94XDIDQ==}
engines: {node: 20 || >=22}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minimatch@3.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-J7p63hRiAjw1NDEww1W7i37+ByIrOWO5XQQAzZ3VOcL0PNybwpfmV/N05zFAzwQ9USyEcX6t3UO+K5aqBQOIHw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minimatch@5.1.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-lKwV/1brpG6mBUFHtb7NUmtABCb2WZZmm2wNiOA5hAb8VdCS4B3dtMWyvcoViccwAW/COERjXLt0zP1zXUN26g==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minimatch@9.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0jWhJpD/MdhPXwPuiRkCbfYfSKp2qnn2eOc279qI7f+osl/l+prKSrvhg157zSYvx/1nmgn2NqdT6k2Z7zSH9w==}
engines: {node: '>=16 || 14 >=14.17'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minimatch@9.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-G6T0ZX48xgozx7587koeX9Ys2NYy6Gmv//P89sEte9V9whIapMNF4idKxnW2QtCcLiTWlb/wfCabAtAFWhhBow==}
engines: {node: '>=16 || 14 >=14.17'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minimist@0.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-miQKw5Hv4NS1Psg2517mV4e4dYNaO3++hjAvLOAzKqZ61rH8NS1SK+vbfBWZ5PY/Me/bEWhUwqMghEW5Fb9T7Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minimist@1.2.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2yyAR8qBkN3YuheJanUpWC5U3bb5osDywNB8RzDVlDwDHbocAJveqqj1u8+SVD7jkWT4yvsHCpWqqWqAxb0zCA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minipass@3.3.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DxiNidxSEK+tHG6zOIklvNOwm3hvCrbUrdtzY74U6HKTJxvIDfOUL5W5P2Ghd3DTkhhKPYGqeNUIh5qcM4YBfw==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minipass@4.2.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fNzuVyifolSLFL4NzpF+wEF4qrgqaaKX0haXPQEdQ7NKAN+WecoKMHV09YcuL/DHxrUsYQOK3MiuDf7Ip2OXfQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minipass@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3FnjYuehv9k6ovOEbyOswadCDPX1piCfhV8ncmYtHOjuPwylVWsghTLo7rabjC3Rx5xD4HDx8Wm1xnMF7S5qFQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minipass@7.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qOOzS1cBTWYF4BH8fVePDBOO9iptMnGUEZwNc/cMWnTV2nVLZ7VoNWEPHkYczZA0pdoA7dl6e7FL659nX9S2aw==}
engines: {node: '>=16 || 14 >=14.17'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minizlib@2.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bAxsR8BVfj60DWXHE3u30oHzfl4G7khkSuPW+qvpd7jFRHm7dLxOjUk1EHACJ/hxLY8phGJ0YhYHZo7jil7Qdg==}
engines: {node: '>= 8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mitt@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vKivATfr97l2/QBCYAkXYDbrIWPM2IIKEl7YPhjCvKlG3kE2gm+uBo6nEXK3M5/Ffh/FLpKExzOQ3JJoJGFKBw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mkcert@3.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-026Eivq9RoOjOuLJGzbhGwXUAjBxRX11Z7Jbm4/7lqT/Av+XNy9SPrJte6+UpEt7i+W3e/HZYxQqlQcqXZWSzg==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
mkdirp-classic@0.5.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gKLcREMhtuZRwRAfqP3RFW+TK4JqApVBtOIftVgjuABpAtpxhPGaDcfvbhNvD0B8iD1oUr/txX35NjcaY6Ns/A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mkdirp@0.5.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-SknJC52obPfGQPnjIkXbmA6+5H15E+fR+E4iR2oQ3zzCLbd7/ONua69R/Gw7AgkTLsRG+r5fzksYwWe1AgTyWA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
hasBin: true
mkdirp@0.5.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FP+p8RB8OWpF3YZBCrP5gtADmtXApB5AMLn+vdyA+PyxCjrCs00mjyUozssO33cwDeT3wNGdLxJ5M//YqtHAJw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
mkdirp@1.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vVqVZQyf3WLx2Shd0qJ9xuvqgAyKPLAiqITEtqW0oIUjzo3PePDd6fW9iFz30ef7Ysp/oiWqbhszeGWW2T6Gzw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
mlly@1.7.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rrVRZRELyQzrIUAVMHxP97kv+G786pHmOKzuFII8zDYahFBS7qnHh2AlYSl1GAHhaMPCz6/oHjVMcfFYgFYHgA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
monaco-editor@0.48.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-goSDElNqFfw7iDHMg8WDATkfcyeLTNpBHQpO8incK6p5qZt5G/1j41X0xdGzpIkGojGXM+QiRQyLjnfDVvrpwA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
moo@0.5.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iSAJLHYKnX41mKcJKjqvnAN9sf0LMDTXDEvFv+ffuRR9a1MIuXLjMNL6EsnDHSkKLTWNqQQ5uo61P4EbU4NU+Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mri@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tzzskb3bG8LvYGFF/mDTpq3jpI6Q9wc3LEmBaghu+DdCssd1FakN7Bc0hVNmEyGq1bq3RgfkCb3cmQLpNPOroA==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mrmime@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hzzEagAgDyoU1Q6yg5uI+AorQgdvMCur3FcKf7NhMKWsaYg+RnbTyHRa/9IlLF9rf455MOCtcqqrQQ83pPP7Uw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mrmime@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eu38+hdgojoyq63s+yTpN4XMBdt5l8HhMhc4VKLO9KM5caLIBvUm4thi7fFaxyTmCKeNnXZ5pAlBwCUnhA09uw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ms@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Tpp60P6IUJDTuOq/5Z8cdskzJujfwqfOTkrwIwj7IRISpnkJnT6SyJ4PCPnGMoFjC9ddhal5KVIYtAt97ix05A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
ms@2.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6FlzubTLZG3J2a/NVCAleEhjzq5oxgHyaCU9yYXvcLsvoVaHJq/s5xXI6/XXP6tz7R9xAOtHnSO/tXtF3WRTlA==}
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
muggle-string@0.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VNTrAak/KhO2i8dqqnqnAHOa3cYBwXEZe9h+D5h/1ZqFSTEFHdM65lR7RoIqq3tBBYavsOXV84NoHXZ0AkPyqQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
murmurhash@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5vQEh3y+DG/lMPM0mCGPDnyV8chYg/g7rl6v3Gd8WMF9S429ox3Xk8qrk174kWhG767KQMqqxLD1WnGd77hiew==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mz@2.7.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-z81GNO7nnYMEhrGh9LeymoE4+Yr0Wn5McHIZMK5cfQCl+NDX08sCZgUc9/6MHni9IWuFLm1Z3HTCXu2z9fN62Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
nanoid@3.3.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eSRppjcPIatRIMC1U6UngP8XFcz8MQWGQdt1MTBQ7NaAmvXDfvNxbvWV3x2y6CdEUciCSsDHDQZbhYaB8QEo2g==}
engines: {node: ^10 || ^12 || ^13.7 || ^14 || >=15.0.1}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
napi-build-utils@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ONmRUqK7zj7DWX0D9ADe03wbwOBZxNAfF20PlGfCWQcD3+/MakShIHrMqx9YwPTfxDdF1zLeL+RGZiR9kGMLdg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
napi-macros@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-A0xLykHtARfueITVDernsAWdtIMbOJgKgcluwENp3AlsKN/PloyO10HtmoqnFAQAcxPkgZN7wdfPfEd0zNGxbg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
natural-compare@1.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-OWND8ei3VtNC9h7V60qff3SVobHr996CTwgxubgyQYEpg290h9J0buyECNNJexkFm5sOajh5G116RYA1c8ZMSw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
nearley@2.20.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+Mc8UaAebFzgV+KpI5n7DasuuQCHA89dmwm7JXw3TV43ukfNQ9DnBH3Mdb2g/I4Fdxc26pwimBWvjIw0UAILSQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
nice-try@1.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1nh45deeb5olNY7eX82BkPO7SSxR5SSYJiPTrTdFUVYwAl8CKMA5N9PjTYkHiRjisVcxcQ1HXdLhx2qxxJzLNQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
no-case@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fgAN3jGAh+RoxUGZHTSOLJIqUc2wmoBwGR4tbpNAKmmovFoWq0OdRkb0VkldReO2a2iBT/OEulG9XSUc10r3zg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
node-abi@3.65.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ThjYBfoDNr08AWx6hGaRbfPwxKV9kVzAzOzlLKbk2CuqXE2xnCh+cbAGnwM3t8Lq4v9rUB7VfondlkBckcJrVA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
node-addon-api@1.7.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ibPK3iA+vaY1eEjESkQkM0BbCqFOaZMiXRTtdB0u7b4djtY6JnsjvPdUHVMg6xQt3B8fpTTWHI9A+ADjM9frzg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
node-addon-api@5.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eh0GgfEkpnoWDq+VY8OyvYhFEzBk6jIYbRKdIlyTiAXIVJ8PyBaKb0rp7oDtoddbdoHWhq8wwr+XZ81F1rpNdA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
node-fetch@2.7.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-c4FRfUm/dbcWZ7U+1Wq0AwCyFL+3nt2bEw05wfxSz+DWpWsitgmSgYmy2dQdWyKC1694ELPqMs/YzUSNozLt8A==}
engines: {node: 4.x || >=6.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
encoding: ^0.1.0
peerDependenciesMeta:
encoding:
optional: true
node-forge@1.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dPEtOeMvF9VMcYV/1Wb8CPoVAXtp6MKMlcbAt4ddqmGqUJ6fQZFXkNZNkNlfevtNkGtaSoXf/vNNNSvgrdXwtA==}
engines: {node: '>= 6.13.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
node-gyp-build@4.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dSq1xmcPDKPZ2EED2S6zw/b9NKsqzXRE6dVr8TVQnI3FJOTteUMuqF3Qqs6LZg+mLGYJWqQzMbIjMtJqTv87nQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
node-ipc@9.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FAyICv0sIRJxVp3GW5fzgaf9jwwRQxAKDJlmNFUL5hOy+W4X/I5AypyHoq0DXXbo9o/gt79gj++4cMr4jVWE/w==}
engines: {node: '>=4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
node-releases@2.0.18:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-d9VeXT4SJ7ZeOqGX6R5EM022wpL+eWPooLI+5UpWn2jCT1aosUQEhQP214x33Wkwx3JQMvIm+tIoVOdodFS40g==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
nopt@7.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-taM24ViiimT/XntxbPyJQzCG+p4EKOpgD3mxFwW38mGjVUrfERQOeY4EDHjdnptttfHuHQXFx+lTP08Q+mLa/w==}
engines: {node: ^14.17.0 || ^16.13.0 || >=18.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
normalize-package-data@2.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/5CMN3T0R4XTj4DcGaexo+roZSdSFW/0AOOTROrjxzCG1wrWXEsGbRKevjlIL+ZDE4sZlJr5ED4YW0yqmkK+eA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
normalize-path@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6eZs5Ls3WtCisHWp9S2GUy8dqkpGi4BVSz3GaqiE6ezub0512ESztXUwUB6C6IKbQkY2Pnb/mD4WYojCRwcwLA==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
normalize-url@6.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DlL+XwOy3NxAQ8xuC0okPgK46iuVNAK01YN7RueYBqqFeGsBjV9XmCAzAdgt+667bCl5kPh9EqKKDwnaPG1I7A==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
npm-run-all@4.1.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Oo82gJDAVcaMdi3nuoKFavkIHBRVqQ1qvMb+9LHk/cF4P6B2m8aP04hGf7oL6wZ9BuGwX1onlLhpuoofSyoQDQ==}
engines: {node: '>= 4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
npm-run-path@5.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ppwTtiJZq0O/ai0z7yfudtBpWIoxM8yE6nHi1X47eFR2EWORqfbu6CnPlNsjeN683eT0qG6H/Pyf9fCcvjnnnQ==}
engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
nth-check@2.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-lqjrjmaOoAnWfMmBPL+XNnynZh2+swxiX3WUE0s4yEHI6m+AwrK2UZOimIRl3X/4QctVqS8AiZjFqyOGrMXb/w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
nwsapi@2.2.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QK0sRs7MKv0tKe1+5uZIQk/C8XGza4DAnztJG8iD+TpJIORARrCxczA738awHrZoHeTjSSoHqao2teO0dC/gFQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
oauth-sign@0.9.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fexhUFFPTGV8ybAtSIGbV6gOkSv8UtRbDBnAyLQw4QPKkgNlsH2ByPGtMUqdWkos6YCRmAqViwgZrJc/mRDzZQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
object-assign@4.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rJgTQnkUnH1sFw8yT6VSU3zD3sWmu6sZhIseY8VX+GRu3P6F7Fu+JNDoXfklElbLJSnc3FUQHVe4cU5hj+BcUg==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
object-hash@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RSn9F68PjH9HqtltsSnqYC1XXoWe9Bju5+213R98cNGttag9q9yAOTzdbsqvIa7aNm5WffBZFpWYr2aWrklWAw==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
object-inspect@1.13.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5qoj1RUiKOMsCCNLV1CBiPYE10sziTsnmNxkAI/rZhiD63CF7IqdFGC/XzjWjpSgLf0LxXX3bDFIh0E18f6UhQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
object-keys@1.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NuAESUOUMrlIXOfHKzD6bpPu3tYt3xvjNdRIQ+FeT0lNb4K8WR70CaDxhuNguS2XG+GjkyMwOzsN5ZktImfhLA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
object.assign@4.1.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-byy+U7gp+FVwmyzKPYhW2h5l3crpmGsxl7X2s8y43IgxvG4g3QZ6CffDtsNQy1WsmZpQbO+ybo0AlW7TY6DcBQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
object.entries@1.1.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cmopxi8VwRIAw/fkijJohSfpef5PdN0pMQJN6VC/ZKvn0LIknWD8KtgY6KlQdEc4tIjcQ3HxSMmnvtzIscdaYQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
object.fromentries@2.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-k6E21FzySsSK5a21KRADBd/NGneRegFO5pLHfdQLpRDETUNJueLXs3WCzyQ3tFRDYgbq3KHGXfTbi2bs8WQ6rQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
object.values@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-yBYjY9QX2hnRmZHAjG/f13MzmBzxzYgQhFrke06TTyKY5zSTEqkOeukBzIdVA3j3ulu8Qa3MbVFShV7T2RmGtQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
on-finished@2.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ikqdkGAAyf/X/gPhXGvfgAytDZtDbr+bkNUJ0N9h5MI/dmdgCs3l6hoHrcUv41sRKew3jIwrp4qQDXiK99Utww==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
on-finished@2.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oVlzkg3ENAhCk2zdv7IJwd/QUD4z2RxRwpkcGY8psCVcCYZNq4wYnVWALHM+brtuJjePWiYF/ClmuDr8Ch5+kg==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
once@1.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-lNaJgI+2Q5URQBkccEKHTQOPaXdUxnZZElQTZY0MFUAuaEqe1E+Nyvgdz/aIyNi6Z9MzO5dv1H8n58/GELp3+w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
onetime@6.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1FlR+gjXK7X+AsAHso35MnyN5KqGwJRi/31ft6x0M194ht7S+rWAvd7PHss9xSKMzE0asv1pyIHaJYq+BbacAQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ono@4.0.11:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jQ31cORBFE6td25deYeD80wxKBMj+zBmHTrVxnc6CKhx8gho6ipmWM5zj/oeoqioZ99yqBls9Z/9Nss7J26G2g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
open@10.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mnkeQ1qP5Ue2wd+aivTD3NHd/lZ96Lu0jgf0pwktLPtx6cTZiH7tyeGRRHs0zX0rbrahXPnXlUnbeXyaBBuIaw==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
opener@1.5.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ur5UIdyw5Y7yEj9wLzhqXiy6GZ3Mwx0yGI+5sMn2r0N0v3cKJvUmFH5yPP+WXh9e0xfyzyJX95D8l088DNFj7A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
optionator@0.9.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6IpQ7mKUxRcZNLIObR0hz7lxsapSSIYNZJwXPGeF0mTVqGKFIXj1DQcMoT22S3ROcLyY/rz0PWaWZ9ayWmad9g==}
engines: {node: '>= 0.8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
p-cancelable@2.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BZOr3nRQHOntUjTrH8+Lh54smKHoHyur8We1V8DSMVrl5A2malOOwuJRnKRDjSnkoeBh4at6BwEnb5I7Jl31wg==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
p-limit@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TYOanM3wGwNGsZN2cVTYPArw454xnXj5qmWF1bEoAc4+cU/ol7GVh7odevjp1FNHduHc3KZMcFduxU5Xc6uJRQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
p-limit@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/Eaoq+QyLSiXQ4lyYV23f14mZRQcXnxfHrN0vCai+ak9G0pp9iEQukIIZq5NccEvwRB8PUnZT0KsOoDCINS1qQ==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
p-locate@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-LaNjtRWUBY++zB5nE/NwcaoMylSPk+S+ZHNB1TzdbMJMny6dynpAGt7X/tl/QYq3TIeE6nxHppbo2LGymrG5Pw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
package-json-from-dist@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dATvCeZN/8wQsGywez1mzHtTlP22H8OEfPrVMLNr4/eGa+ijtLn/6M5f0dY8UKNrC2O9UCU6SSoG3qRKnt7STw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
param-case@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RXlj7zCYokReqWpOPH9oYivUzLYZ5vAPIfEmCTNViosC78F8F0H9y7T7gG2M39ymgutxF5gcFEsyZQSph9Bp3A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parent-module@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GQ2EWRpQV8/o+Aw8YqtfZZPfNRWZYkbidE9k5rpl/hC3vtHHBfGm2Ifi6qWV+coDGkrUKZAxE3Lot5kcsRlh+g==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse-bmfont-ascii@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-U4RrVsUFCleIOBsIGYOMKjn9PavsGOXxbvYGtMOEfnId0SVNsgehXh1DxUdVPLoxd5mvcEtvmKs2Mmf0Mpa1ZA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse-bmfont-binary@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GxmsRea0wdGdYthjuUeWTMWPqm2+FAd4GI8vCvhgJsFnoGhTrLhXDDupwTo7rXVAgaLIGoVHDZS9p/5XbSqeWA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse-bmfont-xml@1.1.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0cEliVMZEhrFDwMh4SxIyVJpqYoOWDJ9P895tFuS+XuNzI5UBmBk5U5O4KuJdTnZpSBI4LFA2+ZiJaiwfSwlMA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse-headers@2.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ft3iAoLOB/MlwbNXgzy43SWGP6sQki2jQvAyBg/zDFAgr9bfNWZIUj42Kw2eJIl8kEi4PbgE6U1Zau/HwI75HA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
parse-imports@2.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TDT4HqzUiTMO1wJRwg/t/hYk8Wdp3iF/ToMIlAoVQfL1Xs/sTxq1dKWSMjMbQmIarfWKymOyly40+zmPHXMqCA==}
engines: {node: '>= 18'}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse-json@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-aOIos8bujGN93/8Ox/jPLh7RwVnPEysynVFE+fQZyg6jKELEHwzgKdLRFHUgXJL6kylijVSBC4BvN9OmsB48Rw==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse-png@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Ge6gDV9T5zhkWHmjvnNiyhPTCIoY7W+FC7qWPtuL2lIGZAFxxqTRG/ouEXsH9qkw+HzYiPEU/tFcxOCEDTP1Yw==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse5@7.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Czj1WaSVpaoj0wbhMzLmWD69anp2WH7FXMB9n1Sy8/ZFF9jolSQVMu1Ij5WIyGmcBmhk7EOndpO4mIpihVqAXw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parseurl@1.3.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CiyeOxFT/JZyN5m0z9PfXw4SCBJ6Sygz1Dpl0wqjlhDEGGBP1GnsUVEL0p63hoG1fcj3fHynXi9NYO4nWOL+qQ==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
partysocket@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sSnLf9X0Oaxw0wXp0liKho0QQqStDJB5I4ViaqmtI4nHm6cpb2kUealErPrcQpYUF6zgTHzLQhIO++2tcJc59A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pascal-case@3.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-uWlGT3YSnK9x3BQJaOdcZwrnV6hPpd8jFH1/ucpiLRPh/2zCVJKS19E4GvYHvaCcACn3foXZ0cLB9Wrx1KGe5g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-browserify@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-b7uo2UCUOYZcnF/3ID0lulOJi/bafxa1xPe7ZPsammBSpjSWQkjNxlt635YGS2MiR9GjvuXCtz2emr3jbsz98g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-case@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qO4qCFjXqVTrcbPt/hQfhTQ+VhFsqNKOPtytgNKkKxSoEp3XPUQ8ObFuePylOIok5gjn69ry8XiULxCwot3Wfg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-exists@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ak9Qy5Q7jYb2Wwcey5Fpvg2KoAc/ZIhLSLOSBmRmygPsGwkVVt0fZa0qrtMz+m6tJTAHfZQ8FnmB4MG4LWy7/w==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-is-absolute@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AVbw3UJ2e9bq64vSaS9Am0fje1Pa8pbGqTTsmXfaIiMpnr5DlDhfJOuLj9Sf95ZPVDAUerDfEk88MPmPe7UCQg==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-key@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fEHGKCSmUSDPv4uoj8AlD+joPlq3peND+HRYyxFz4KPw4z926S/b8rIuFs2FYJg3BwsxJf6A9/3eIdLaYC+9Dw==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-key@3.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ojmeN0qd+y0jszEtoY48r0Peq5dwMEkIlCOu6Q5f41lfkswXuKtYrhgoTpLnyIcHm24Uhqx+5Tqm2InSwLhE6Q==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-key@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-haREypq7xkM7ErfgIyA0z+Bj4AGKlMSdlQE2jvJo6huWD1EdkKYV+G/T4nq0YEF2vgTT8kqMFKo1uHn950r4SQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-parse@1.0.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-LDJzPVEEEPR+y48z93A0Ed0yXb8pAByGWo/k5YYdYgpY2/2EsOsksJrq7lOHxryrVOn1ejG6oAp8ahvOIQD8sw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-scurry@1.11.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Xa4Nw17FS9ApQFJ9umLiJS4orGjm7ZzwUrwamcGQuHSzDyth9boKDaycYdDcZDuqYATXw4HFXgaqWTctW/v1HA==}
engines: {node: '>=16 || 14 >=14.18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
path-scurry@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ypGJsmGtdXUOeM5u93TyeIEfEhM6s+ljAhrk5vAvSx8uyY/02OvrZnA0YNGUrPXfpJMgI1ODd3nwz8Npx4O4cg==}
engines: {node: 20 || >=22}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-type@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-T2ZUsdZFHgA3u4e5PfPbjd7HDDpxPnQb5jN0SrDsjNSuVXHJqtwTnWqG0B1jZrgmJ/7lj1EmVIByWt1gxGkWvg==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-type@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gDKb8aZMDeD/tZWs9P6+q0J9Mwkdl6xMV8TjnGP3qJVJ06bdMgkbBlLU8IdfOsIsFz2BW1rNVT3XuNEl8zPAvw==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pathe@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-whLdWMYL2TwI08hn8/ZqAbrVemu0LNaNNJZX73O6qaIdCTfXutsLhMkjdENX0qhsQ9uIimo4/aQOmXkoon2nDQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pathval@1.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Dp6zGqpTdETdR63lehJYPeIOqpiNBNtc7BpWSLrOje7UaIsE5aY92r/AunQA7rsXvet3lrJ3JnZX29UPTKXyKQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pend@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-F3asv42UuXchdzt+xXqfW1OGlVBe+mxa2mqI0pg5yAHZPvFmY3Y6drSf/GQ1A86WgWEN9Kzh/WrgKa6iGcHXLg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
perfect-debounce@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xCy9V055GLEqoFaHoC1SoLIaLmWctgCUaBaWxDZ7/Zx4CTyX7cJQLJOok/orfjZAh9kEYpjJa4d0KcJmCbctZA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
performance-now@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7EAHlyLHI56VEIdK57uwHdHKIaAGbnXPiw0yWbarQZOKaKpvUIgW0jWRVLiatnM+XXlSwsanIBH/hzGMJulMow==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
phin@2.9.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CzFr90qM24ju5f88quFC/6qohjC144rehe5n6DH900lgXmUe86+xCKc10ev56gRKC4/BkHUoG4uSiQgBiIXwDA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
picocolors@1.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TQ92mBOW0l3LeMeyLV6mzy/kWr8lkd/hp3mTg7wYK7zJhuBStmGMBG0BdeDZS/dZx1IukaX6Bk11zcln25o1Aw==}
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
picomatch@2.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JU3teHTNjmE2VCGFzuY8EXzCDVwEqB2a8fsIvwaStHhAWJEeVd1o1QD80CU6+ZdEXXSLbSsuLwJjkCBWqRQUVA==}
engines: {node: '>=8.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pidtree@0.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qQbW94hLHEqCg7nhby4yRC7G2+jYHY4Rguc2bjw7Uug4GIJuu1tvf2uHaZv5Q8zdt+WKJ6qK1FOI6amaWUo5FA==}
engines: {node: '>=0.10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
pify@2.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-udgsAY+fTnvv7kI7aaxbqwWNb0AHiB0qBO89PZKPkoTmGOgdbrHDKD+0B2X4uTfJ/FT1R09r9gTsjUjNJotuog==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pify@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-C3FsVNH1udSEX48gGX1xfvwTWfsYWj5U+8/uK15BGzIGrKoUpghX8hWZwa/OFnakBiiVNmBvemTJR5mcy7iPcg==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pinkie-promise@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0Gni6D4UcLTbv9c57DfxDGdr41XfgUjqWZu492f0cIGr16zDU06BWP/RAEvOuo7CQ0CNjHaLlM59YJJFm3NWlw==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pinkie@2.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MnUuEycAemtSaeFSjXKW/aroV7akBbY+Sv+RkyqFjgAe73F+MR0TBWKBRDkmfWq/HiFmdavfZ1G7h4SPZXaCSg==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pirates@4.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-saLsH7WeYYPiD25LDuLRRY/i+6HaPYr6G1OUlN39otzkSTxKnubR9RTxS3/Kk50s1g2JTgFwWQDQyplC5/SHZg==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pixelmatch@4.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-J8B6xqiO37sU/gkcMglv6h5Jbd9xNER7aHzpfRdNmV4IbQBzBpe4l9XmbG+xPF/znacgu2jfEw+wHffaq/YkXA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
pkg-types@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VEGf1he2DR5yowYRl0XJhWJq5ktm9gYIsH+y8sNJpHlxch7JPDaufgrsl4vYjd9hMUY8QVjoNncKbow9I7exyA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
playwright-core@1.45.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-lZmHlFQ0VYSpAs43dRq1/nJ9G/6SiTI7VPqidld9TDefL9tX87bTKExWZZUF5PeRyqtXqd8fQi2qmfIedkwsNQ==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
playwright@1.45.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4z3ac3plDfYzGB6r0Q3LF8POPR20Z8D0aXcxbJvmfMgSSq1hkcgvFRXJk9rUq5H/MJ0Ktal869hhOdI/zUTeLA==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
plist@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-uysumyrvkUX0rX/dEVqt8gC3sTBzd4zoWfLeS29nb53imdaXVvLINYXTI2GNqzaMuvacNx4uJQ8+b3zXR0pkgQ==}
engines: {node: '>=10.4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pngjs@3.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NCrCHhWmnQklfH4MtJMRjZ2a8c80qXeMlQMv2uVp9ISJMTt562SbGd6n2oq0PaPgKm7Z6pL9E2UlLIhC+SHL3w==}
engines: {node: '>=4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
portfinder@1.0.32:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-on2ZJVVDXRADWE6jnQaX0ioEylzgBpQk8r55NE4wjXW1ZxO+BgDlY6DXwj20i0V8eB4SenDQ00WEaxfiIQPcxg==}
engines: {node: '>= 0.12.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
possible-typed-array-names@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-d7Uw+eZoloe0EHDIYoe+bQ5WXnGMOpmiZFTuMWCwpjzzkL2nTjcKiAk4hh8TjnGye2TwWOk3UXucZ+3rbmBa8Q==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
postcss-import@15.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hpr+J05B2FVYUAXHeK1YyI267J/dDDhMU6B6civm8hSY1jYJnBXxzKDKDswzJmtLHryrjhnDjqqp/49t8FALew==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
postcss: ^8.0.0
postcss-inline-svg@6.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ok5j0Iqsn8mS/5U1W+Im6qkQjm6nBxdwwJU+BSnBaDhLjC06h1xvy9MA+tefxhfZP/ARTRwARSozzYGf/sqEGg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
postcss: ^8.1.4
postcss-js@4.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dDLF8pEO191hJMtlHFPRa8xsizHaM82MLfNkUHdUtVEV3tgTp5oj+8qbEqYM57SLfc74KSbw//4SeJma2LRVIw==}
engines: {node: ^12 || ^14 || >= 16}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
postcss: ^8.4.21
postcss-load-config@4.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bSVhyJGL00wMVoPUzAVAnbEoWyqRxkjv64tUl427SKnPrENtq6hJwUojroMz2VB+Q1edmi4IfrAPpami5VVgMQ==}
engines: {node: '>= 14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
postcss: '>=8.0.9'
ts-node: '>=9.0.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
postcss:
optional: true
ts-node:
optional: true
postcss-nested@6.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mEp4xPMi5bSWiMbsgoPfcP74lsWLHkQbZc3sY+jWYd65CUwXrUaTp0fmNpa01ZcETKlIgUdFN/MpS2xZtqL9dQ==}
engines: {node: '>=12.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
postcss: ^8.2.14
postcss-nesting@12.1.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-N1NgI1PDCiAGWPTYrwqm8wpjv0bgDmkYHH72pNsqTCv9CObxjxftdYu6AKtGN+pnJa7FQjMm3v4sp8QJbFsYdQ==}
engines: {node: ^14 || ^16 || >=18}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
postcss: ^8.4
postcss-selector-parser@6.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UMz42UD0UY0EApS0ZL9o1XnLhSTtvvvLe5Dc2H2O56fvRZi+KulDyf5ctDhhtYJBGKStV2FL1fy6253cmLgqVQ==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
postcss-value-parser@4.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1NNCs6uurfkVbeXG4S8JFT9t19m45ICnif8zWLd5oPSZ50QnwMfK+H3jv408d4jw/7Bttv5axS5IiHoLaVNHeQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
postcss@8.4.45:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7KTLTdzdZZYscUc65XmjFiB73vBhBfbPztCYdUNvlaso9PrzjzcmjqBPR0lNGkcVlcO4BjiO5rK/qNz+XAen1Q==}
engines: {node: ^10 || ^12 || >=14}
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prebuild-install@7.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UnNke3IQb6sgarcZIDU3gbMeTp/9SSU1DAIkil7PrqG1vZlBtY5msYccSKSHDqa3hNg436IXK+SNImReuA1wEQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
prelude-ls@1.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vkcDPrRZo1QZLbn5RLGPpg/WmIQ65qoWWhcGKf/b5eplkkarX0m9z8ppCat4mlOqUsWpyNuYgO3VRyrYHSzX5g==}
engines: {node: '>= 0.8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prettier-linter-helpers@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GbK2cP9nraSSUF9N2XwUwqfzlAFlMNYYl+ShE/V+H8a9uNl/oUqB1w2EL54Jh0OlyRSd8RfWYJ3coVS4TROP2w==}
engines: {node: '>=6.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prettier-plugin-organize-imports@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vnKSdgv9aOlqKeEFGhf9SCBsTyzDSyScy1k7E0R1Uo4L0cTcOV7c1XQaT7jfXIOc/p08WLBfN2QUQA9zDSZMxA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/language-plugin-pug': ^2.0.24
prettier: '>=2.0'
typescript: '>=2.9'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vue-tsc: ^2.0.24
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/language-plugin-pug':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
vue-tsc:
optional: true
prettier-plugin-tailwindcss@0.5.14:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Puaz+wPUAhFp8Lo9HuciYKM2Y2XExESjeT+9NQoVFXZsPPnc9VYss2SpxdQ6vbatmt8/4+SN0oe0I1cPDABg9Q==}
engines: {node: '>=14.21.3'}
peerDependencies:
'@ianvs/prettier-plugin-sort-imports': '*'
'@prettier/plugin-pug': '*'
'@shopify/prettier-plugin-liquid': '*'
'@trivago/prettier-plugin-sort-imports': '*'
'@zackad/prettier-plugin-twig-melody': '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prettier: ^3.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
prettier-plugin-astro: '*'
prettier-plugin-css-order: '*'
prettier-plugin-import-sort: '*'
prettier-plugin-jsdoc: '*'
prettier-plugin-marko: '*'
prettier-plugin-organize-attributes: '*'
prettier-plugin-organize-imports: '*'
prettier-plugin-sort-imports: '*'
prettier-plugin-style-order: '*'
prettier-plugin-svelte: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ianvs/prettier-plugin-sort-imports':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@prettier/plugin-pug':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@shopify/prettier-plugin-liquid':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@trivago/prettier-plugin-sort-imports':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@zackad/prettier-plugin-twig-melody':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
prettier-plugin-astro:
optional: true
prettier-plugin-css-order:
optional: true
prettier-plugin-import-sort:
optional: true
prettier-plugin-jsdoc:
optional: true
prettier-plugin-marko:
optional: true
prettier-plugin-organize-attributes:
optional: true
prettier-plugin-organize-imports:
optional: true
prettier-plugin-sort-imports:
optional: true
prettier-plugin-style-order:
optional: true
prettier-plugin-svelte:
optional: true
prettier@3.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rAVeHYMcv8ATV5d508CFdn+8/pHPpXeIid1DdrPwXnaAdH7cqjVbpJaT5eq4yRAFU/lsbwYwSF/n5iNrdJHPQA==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
pretty-format@29.7.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Pdlw/oPxN+aXdmM9R00JVC9WVFoCLTKJvDVLgmJ+qAffBMxsV85l/Lu7sNx4zSzPyoL2euImuEwHhOXdEgNFZQ==}
engines: {node: ^14.15.0 || ^16.10.0 || >=18.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
process-nextick-args@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3ouUOpQhtgrbOa17J7+uxOTpITYWaGP7/AhoR3+A+/1e9skrzelGi/dXzEYyvbxubEF6Wn2ypscTKiKJFFn1ag==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
process@0.11.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cdGef/drWFoydD1JsMzuFf8100nZl+GT+yacc2bEced5f9Rjk4z+WtFUTBu9PhOi9j/jfmBPu0mMEY4wIdAF8A==}
engines: {node: '>= 0.6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
progress@2.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7PiHtLll5LdnKIMw100I+8xJXR5gW2QwWYkT6iJva0bXitZKa/XMrSbdmg3r2Xnaidz9Qumd0VPaMrZlF9V9sA==}
engines: {node: '>=0.4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
promise-retry@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-y+WKFlBR8BGXnsNlIHFGPZmyDf3DFMoLhaflAnyZgV6rG6xu+JwesTo2Q9R6XwYmtmwAFCkAk3e35jEdoeh/3g==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prop-types@15.8.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oj87CgZICdulUohogVAR7AjlC0327U4el4L6eAvOqCeudMDVU0NThNaV+b9Df4dXgSP1gXMTnPdhfe/2qDH5cg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
proto-list@1.2.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vtK/94akxsTMhe0/cbfpR+syPuszcuwhqVjJq26CuNDgFGj682oRBXOP5MJpv2r7JtE8MsiepGIqvvOTBwn2vA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prr@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-yPw4Sng1gWghHQWj0B3ZggWUm4qVbPwPFcRG8KyxiU7J2OHFSoEHKS+EZ3fv5l1t9CyCiop6l/ZYeWbrgoQejw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
psl@1.9.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-E/ZsdU4HLs/68gYzgGTkMicWTLPdAftJLfJFlLUAAKZGkStNU72sZjT66SnMDVOfOWY/YAoiD7Jxa9iHvngcag==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pump@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-LwZy+p3SFs1Pytd/jYct4wpv49HiYCqd9Rlc5ZVdk0V+8Yzv6jR5Blk3TRmPL1ft69TxP0IMZGJ+WPFU2BFhww==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
punycode@1.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RofWgt/7fL5wP1Y7fxE7/EmTLzQVnB0ycyibJ0OOHIlJqTNzglYFxVwETOcIoJqJmpDXJ9xImDv+Fq34F/d4Dw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
punycode@1.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jmYNElW7yvO7TV33CjSmvSiE2yco3bV2czu/OzDKdMNVZQWfxCblURLhf+47syQRBntjfLdd/H0egrzIG+oaFQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
punycode@2.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vYt7UD1U9Wg6138shLtLOvdAu+8DsC/ilFtEVHcH+wydcSpNE20AfSOduf6MkRFahL5FY7X1oU7nKVZFtfq8Fg==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pure-rand@6.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bVWawvoZoBYpp6yIoQtQXHZjmz35RSVHnUOTefl8Vcjr8snTPY1wnpSPMWekcFwbxI6gtmT7rSYPFvz71ldiOA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
MFA (#10875) * Draft checkbox component * Fixes in Setup Page * Invite Users * Add usergroup setup after subscription * Fix comments * Refetch Interval + Feature Toggles * Fix lint * Address issues * Fix Dialog * Assign users to the user group * Use transitions to navigate between steps * Small fixes * Improve styling for scrollbars * Fix typescript * OTP input * Fix setup logic * Show Setup dialog only for admins * Add otp * OTP input * 2FA settings section * Small improvements * Fixes * Small fixes * Remove w-full * TOTP at login * Fixes in 2FA * Fixes in types * Fix totp * Merge fixes * Merge fixes x2 * Merge fixes x2 * Fix types * Fix types * Fix cancel button * Fix reset button * Fix types * Fix prettier * Fix prettier * Fix lint * Fix lint * Fix control * Address prettier * Fix MFA mock * Fix sign in message * Fix tests * Address CR * Fix types
2024-09-13 16:00:31 +03:00
qrcode.react@3.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oyF+Urr3oAMUG/OiOuONL3HXM+53wvuH3mtIWQrYmsXoAq0DkvZp2RYUWFSMFtbdOpuS++9v+WAkzNVkMlNW6Q==}
MFA (#10875) * Draft checkbox component * Fixes in Setup Page * Invite Users * Add usergroup setup after subscription * Fix comments * Refetch Interval + Feature Toggles * Fix lint * Address issues * Fix Dialog * Assign users to the user group * Use transitions to navigate between steps * Small fixes * Improve styling for scrollbars * Fix typescript * OTP input * Fix setup logic * Show Setup dialog only for admins * Add otp * OTP input * 2FA settings section * Small improvements * Fixes * Small fixes * Remove w-full * TOTP at login * Fixes in 2FA * Fixes in types * Fix totp * Merge fixes * Merge fixes x2 * Merge fixes x2 * Fix types * Fix types * Fix cancel button * Fix reset button * Fix types * Fix prettier * Fix prettier * Fix lint * Fix lint * Fix control * Address prettier * Fix MFA mock * Fix sign in message * Fix tests * Address CR * Fix types
2024-09-13 16:00:31 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0 || ^18.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
qs@6.11.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MvjoMCJwEarSbUYk5O+nmoSzSutSsTwF85zcHPQ9OrlFoZOYIjaqBAJIqIXjptyD5vThxGq52Xu/MaJzRkIk4Q==}
engines: {node: '>=0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
qs@6.12.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-zWmv4RSuB9r2mYQw3zxQuHWeU+42aKi1wWig/j4ele4ygELZ7PEO6MM7rim9oAQH2A5MWfsAVf/jPvTPgCbvUQ==}
engines: {node: '>=0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
qs@6.5.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qxXIEh4pCGfHICj1mAJQ2/2XVZkjCDTcEgfoSQxc/fYivUZxTkk7L3bDBJSoNrEzXI17oUO5Dp07ktqE5KzczA==}
engines: {node: '>=0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
querystring@0.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-X/xY82scca2tau62i9mDyU9K+I+djTMUsvwf7xnUX5GLvVzgJybOJf4Y6o9Zx3oJK/LSXg5tTZBjwzqVPaPO2g==}
engines: {node: '>=0.4.x'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
querystringify@2.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FIqgj2EUvTa7R50u0rGsyTftzjYmv/a3hO345bZNrqabNqjtgiDMgmo4mkUjd+nzU5oF3dClKqFIPUKybUyqoQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
queue-microtask@1.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NuaNSa6flKT5JaSYQzJok04JzTL1CA6aGhv5rfLW3PgqA+M2ChpZQnAC8h8i4ZFkBS8X5RqkDBHA7r4hej3K9A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
quick-lru@5.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WuyALRjWPDGtt/wzJiadO5AXY+8hZ80hVpe6MyivgraREW751X3SbhRvG3eLKOYN+8VEvqLcf3wdnt44Z4S4SA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
railroad-diagrams@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cz93DjNeLY0idrCNOH6PviZGRN9GJhsdm9hpn1YCS879fj4W+x5IFJhhkRZcwVgMmFF7R82UA/7Oh+R8lLZg6A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
randexp@0.4.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-80WNmd9DA0tmZrw9qQa62GPPWfuXJknrmVmLcxvq4uZBdYqb1wYoKTmnlGUchvVWe0XiLupYkBoXVOxz3C8DYQ==}
engines: {node: '>=0.12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
raw-body@2.5.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8zGqypfENjCIqGhgXToC8aB2r7YrBX+AQAfIPs/Mlk+BtPTztOvTS01NRW/3Eh60J+a48lt8qsCzirQ6loCVfA==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
rc@1.2.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-y3bGgqKj3QBdxLbLkomlohkvsA8gdAiUQlSBJnBhfn+BPxg4bc62d8TcBW15wavDfgexCgccckhcZvywyQYPOw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react-aria-components@1.3.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wNjcoyIFTL14Z07OJ1I5m37CYB+1oH2DW8PIgZQjGt9lLcYKKEBLSgsenHVKu1F1L9tqlpXgYk5TeXCzU/xUKw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react-aria@3.34.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wSprEI5EojDFCm357MxnKAxJZN68OYIt6UH6N0KCo6MEUAVZMbhMSmGYjw/kLK4rI7KrbJDqGqUMQkwc93W9Ng==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
react-dom: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
react-compiler-runtime@19.0.0-beta-6fc168f-20241025:
resolution: {integrity: sha512-XY5p6GUVaz8P0c/B/2ebqz/xdp0YOtidtOSuiYyQB05fMws0Qys+zubDH7IKQBEtw4AKoCzrJ6ReeTtFLOKniw==}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
peerDependencies:
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
react: ^17.0.0 || ^18.0.0 || ^19.0.0
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-dom@18.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5m4nQKp+rZRb09LNH59GM4BxTh9251/ylbKIbpe7TpGxfJ+9kv6BLkLBXIjjspbgbnIBNqlI23tRnTWT0snUIw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
react: ^18.3.1
react-error-boundary@4.0.13:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-b6PwbdSv8XeOSYvjt8LpgpKrZ0yGdtZokYwkwV2wlcZbxgopHX/hgPl5VgpnoVOWd868n1hktM8Qm4b+02MiLQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
react: '>=16.13.1'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-hook-form@7.52.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-mJX506Xc6mirzLsmXUJyqlAI3Kj9Ph2RhplYhUVffeOQSnubK2uVqBFOBJmvKikvbFV91pxVXmDiR+QMF19x6A==}
engines: {node: '>=12.22.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
react: ^16.8.0 || ^17 || ^18 || ^19
react-is@16.13.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-24e6ynE2H+OKt4kqsOvNd8kBpV65zoxbA4BVsEOB3ARVWQki/DHzaUoC5KuON/BiccDaCCTZBuOcfZs70kR8bQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-is@18.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/LLMVyas0ljjAtoYiPqYiL8VWXzUUdThrmU5+n20DZv+a+ClRoevUzw5JxU+Ieh5/c87ytoTBV9G1FiKfNJdmg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-refresh@0.14.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jCvmsr+1IUSMUyzOkRcvnVbX3ZYC6g9TDrDbFuFmRDq7PD4yaGbLKNQL6k2jnArV8hjYxh7hVhAZB6s9HDGpZA==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-router-dom@6.24.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-960sKuau6/yEwS8e+NVEidYQb1hNjAYM327gjEyXlc6r3Skf2vtwuJ2l7lssdegD2YjoKG5l8MsVyeTDlVeY8g==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
react: '>=16.8'
react-dom: '>=16.8'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-router@6.24.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sQrgJ5bXk7vbcC4BxQxeNa5UmboFm35we1AFK0VvQaz9g0LzxEIuLOhHIoZ8rnu9BO21ishGeL9no1WB76W/eg==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
react: '>=16.8'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react-stately@3.32.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pDSrbCIJtir4HeSa//PTqLSR7Tl7pFC9usmkkBObNKktObQq3Vdgkf46cxeTD1ov7J7GDdR3meIyjXGnZoEzUg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: ^16.8.0 || ^17.0.0-rc.1 || ^18.0.0 || ^19.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-toastify@9.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fPfb8ghtn/XMxw3LkxQBk3IyagNpF/LIKjOBflbexr2AWxAH1MJgvnESwEwBn9liLFXgTKWgBSdZpw9m4OTHTg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
react: '>=16'
react-dom: '>=16'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react@18.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wS+hAgJShR0KhEvPJArfuPVN1+Hz1t0Y6n5jLrGQbkb4urgPE/0Rve+1kMB1v/oWgHgm4WIcV+i7F2pTVj+2iQ==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
read-cache@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Owdv/Ft7IjOgm/i0xvNDZ1LrRANRfew4b2prF3OWMQLxLfu3bS8FVhCsrSCMK4lR56Y9ya+AThoTpDCTxCmpRA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
read-chunk@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5NLTTdX45dKFtG8CX5pKmvS9V5u9wBE+gkklN7xhDuhq3pA2I4O7ALfKxosCMcLHOhkxj6GNacZhfXtp5nlCdg==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
read-config-file@6.3.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-M80lpCjnE6Wt6zb98DoW8WHR09nzMSpu8XHtPkiTHrJ5Az9CybfeQhTJ8D7saeBHpGhLPIVyA8lcL6ZmdKwY6Q==}
engines: {node: '>=12.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
read-pkg@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BLq/cCO9two+lBgiTYNqD6GdtK8s4NpaWrl6/rCO9w0TUS8oJl7cmToOZfRYllKTISY6nt1U7jQ53brmKqY6BA==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
readable-stream@2.3.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8p0AUk4XODgIewSi0l8Epjs+EVnWiK7NoDIEGU0HhE7+ZyY8D1IMY7odu5lRrFXGg71L15KG8QrPmum45RTtdA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
readable-stream@3.6.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9u/sniCrY3D5WdsERHzHE4G2YCXqoG5FTHUiCC4SIbr6XcLZBY05ya9EKjYek9O5xOAwjGq+1JdGBAS7Q9ScoA==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
readdir-glob@1.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-v05I2k7xN8zXvPD9N+z/uhXPaj0sUFCe2rcWZIpBsqxfP7xXFQ0tipAd/wjj1YxWyWtUS5IDJpOG82JKt2EAVA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
readdirp@3.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hOS089on8RduqdbhvQ5Z37A0ESjsqz6qnRcffsMU3495FuTdqSm+7bhJ29JvIOsBDEEnan5DPu9t3To9VRlMzA==}
engines: {node: '>=8.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
reflect.getprototypeof@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fmfw4XgoDke3kdI6h4xcUz1dG8uaiv5q9gcEwLS4Pnth2kxT+GZ7YehS1JTMGBQmtV7Y4GFGbs2re2NqhdozUg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
regenerator-runtime@0.14.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dYnhHh0nJoMfnkZs6GmmhFknAGRrLznOu5nc9ML+EJxGvrx6H7teuevqVqCuPcPK//3eDrrjQhehXVx9cnkGdw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
regexp.prototype.flags@1.5.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NcDiDkTLuPR+++OCKB0nWafEmhg/Da8aUPLPMQbK+bxKKCm1/S5he+AqYa4PlMCVBalb4/yxIRub6qkEx5yJbw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
remove-accents@0.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8g3/Otx1eJaVD12e31UbJj1YzdtVvzH85HV7t+9MJYk/u3XmkOUJ5Ys9wQrf9PCPK8+xn4ymzqYCiZl6QWKn+A==}
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
request@2.88.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MsvtOrfG9ZcrOwAW+Qi+F6HbD0CWXEh9ou77uOb7FM2WPhwT7smM833PzanhJLsgXjN89Ir6V2PczXNnMpwKhw==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: request has been deprecated, see https://github.com/request/request/issues/3142
require-directory@2.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fGxEI7+wsG9xrvdjsrlmL22OMTTiHRwAMroiEeMgq8gzoLC/PQr7RsRDSTLUg/bZAZtF+TVIkHc6/4RIKrui+Q==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
require-from-string@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Xf0nWe6RseziFMu+Ap9biiUbmplq6S9/p+7w7YXP/JBHhrUDDUhwa+vANyubuqfZWTveU//DYVGsDG7RKL/vEw==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
requires-port@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KigOCHcocU3XODJxsu8i/j8T9tzT4adHiecwORRQ0ZZFcp7ahwXuRU1m+yuO90C5ZUyGeGfocHDI14M3L3yDAQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
resize-img@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/4nKUmuNPuM6gYTWad136ica81baOVjpesgv8FGaIvP0KWcbCWahOWBKaM4tFoM+aVcSA+qQDg28pcnIzFRpJw==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
resolve-alpn@1.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0a1F4l73/ZFZOakJnQ3FvkJ2+gSTQWz/r2KE5OdDY0TxPm5h4GkqkWWfM47T7HsbnOtcJVEF4epCVy6u7Q3K+g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
resolve-from@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pb/MYmXstAkysRFx8piNI1tGFNQIFA3vkE3Gq4EuA1dF6gHp/+vgZqsCGJapvy8N3Q+4o7FwvquPJcnZ7RYy4g==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
resolve-pkg-maps@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-seS2Tj26TBVOC2NIc2rOe2y2ZO7efxITtLZcGSOnHHNOQ7CkiUBfw0Iw2ck6xkIhPwLhKNLS8BO+hEpngQlqzw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
resolve@1.22.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oKWePCxqpd6FlLvGV1VU0x7bkPmmCNolxzjMf4NczoDnQcIWrAF+cPtZn5i6n+RfD2d9i0tzpKnG6Yk168yIyw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
resolve@2.0.0-next.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-U7WjGVG9sH8tvjW5SmGbQuui75FiyjAX72HX15DwBBwF9dNiQZRQAg9nnPhYy+TUnE0+VcrttuvNI8oSxZcocA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
responselike@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4gl03wn3hj1HP3yzgdI7d3lCkF95F21Pz4BPGvKHinyQzALR5CapwC8yIi0Rh58DEMQ/SguC03wFj2k0M/mHhw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ret@0.1.15:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TTlYpa+OL+vMMNG24xSlQGEJ3B/RzEfUlLct7b5G/ytav+wPrplCpVMFuwzXbkecJrb6IYo1iFb0S9v37754mg==}
engines: {node: '>=0.12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
retry@0.12.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9LkiTwjUh6rT555DtE9rTX+BKByPfrMzEAtnlEtdEwr3Nkffwiihqe2bWADg+OQRjt9gl6ICdmB/ZFDCGAtSow==}
engines: {node: '>= 4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
reusify@1.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-U9nH88a3fc/ekCF1l0/UP1IosiuIjyTh7hBvXVMHYgVcfGvt897Xguj2UOLDeI5BG2m7/uwyaLVT6fbtCwTyzw==}
engines: {iojs: '>=1.0.0', node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
rfdc@1.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-q1b3N5QkRUWUl7iyylaaj3kOpIT0N2i9MqIEQXP73GVsN9cw3fdx8X63cEmWhJGi2PPCF23Ijp7ktmd39rawIA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
rimraf@6.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9dkvaxAsk/xNXSJzMgFqqMCuFgt2+KsOFek3TMLfo8NCPfWpBmqwyNn5Y+NX56QUYfCtsyhF3ayiboEoUmJk/A==}
engines: {node: 20 || >=22}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
roarr@2.15.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CHhPh+UNHD2GTXNYhPWLnU8ONHdI+5DI+4EYIAOaiD63rHeYlZvyh8P+in5999TTSFgUYuKUAjzRI4mdh/p+2A==}
engines: {node: '>=8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
robust-predicates@3.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-IXgzBWvWQwE6PrDI05OvmXUIruQTcoMDzRsOd5CDvHCVLcLHMTSYvOK5Cm46kWqlV3yAbuSpBZdJ5oP5OUoStg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
rollup@4.24.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DOmrlGSXNk1DM0ljiQA+i+o0rSLhtii1je5wgk60j49d1jHT5YYttBv1iWOnYSTG+fZZESUOSNiAl89SIet+Cg==}
engines: {node: '>=18.0.0', npm: '>=8.0.0'}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
hasBin: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
rrweb-cssom@0.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-APM0Gt1KoXBz0iIkkdB/kfvGOwC4UuJFeG/c+yV7wSc7q96cG/kJ0HiYCnzivD9SB53cLV1MlHFNfOuPaadYSw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
rrweb-cssom@0.7.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TrEMa7JGdVm0UThDJSx7ddw5nVm3UJS9o9CCIZ72B1vSyEZoziDqBYP3XIoi/12lKrJR8rE3jeFHMok2F/Mnsg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
run-applescript@7.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9by4Ij99JUr/MCFBUkDKLWK3G9HVXmabKz9U5MlIAIuvuzkiOicRYs8XJLxX+xahD+mLiiCYDqF9dKAgtzKP1A==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
run-parallel@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5l4VyZR86LZ/lDxZTR6jqL8AFE2S0IFLMP26AbjsLVADxHdhB/c0GUsH+y39UfCi3dzz8OlQuPmnaJOMoDHQBA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
rw@1.3.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PdhdWy89SiZogBLaw42zdeqtRJ//zFd2PgQavcICDUgJT5oW10QCRKbJ6bg4r0/UY2M6BWd5tkxuGFRvCkgfHQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sade@1.8.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xal3CZX1Xlo/k4ApwCFrHVACi9fBqJ7V+mwhBsuf/1IOKbBy098Fex+Wa/5QMubw09pSZ/u8EY8PWgevJsXp1A==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
safe-array-concat@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vj6RsCsWBCf19jIeHEfkRMw8DPiBb+DMXklQ/1SGDHOMlHdPUkZXFQ2YdplS23zESTijAcurb1aSgJA3AgMu1Q==}
engines: {node: '>=0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
safe-buffer@5.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Gd2UZBJDkXlY7GbJxfsE8/nvKkUEU1G38c1siN6QP6a9PT9MmHB8GnpscSmMJSoF8LOIrt8ud/wPtojys4G6+g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
safe-buffer@5.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rp3So07KcdmmKbGvgaNxQSJr7bGVSVk5S9Eq1F+ppbRo70+YeaDxkw5Dd8NPN+GD6bjnYm2VuPuCXmpuYvmCXQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
safe-regex-test@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CdASjNJPvRa7roO6Ra/gLYBTzYzzPyyBXxIMdGW3USQLyjWEls2RgW5UBTXaQVp+OrpeCK3bLem8smtmheoRuw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
safer-buffer@2.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YZo3K82SD7Riyi0E1EQPojLz7kpepnSQI9IyPbHHg1XXXevb5dJI7tpyN2ADxGcQbHG7vcyRHk0cbwqcQriUtg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sanitize-filename@1.6.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-y/52Mcy7aw3gRm7IrcGDFx/bCk4AhRh2eI9luHOQM86nZsqwiRkkq2GekHXBBD+SmPidc8i2PqtYZl+pWJ8Oeg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sax@1.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+aWOz7yVScEGoKNd4PA10LZ8sk0A/z5+nXQG5giUO5rprX9jgYsTdov9qCchZiPIZezbZH+jRut8nPodFAX4Jg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
saxes@6.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xAg7SOnEhrm5zI3puOOKyy1OMcMlIJZYNJY7xLBwSze0UjhPLnWfj2GF2EpT0jmzaJKIWKHLsaSSajf35bcYnA==}
engines: {node: '>=v12.22.7'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
scheduler@0.23.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UOShsPwz7NrMUqhR6t0hWjFduvOzbtv7toDH1/hIrfRNIDBnnBWd0CwJTGvTpngVlmwGCdP9/Zl/tVrDqcuYzQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
section-matter@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vfD3pmTzGpufjScBh50YHKzEu2lxBWhVEHsNGoEXmCmn2hKGfeNLYMzCJpe8cD7gqX7TJluOVpBkAequ6dgMmA==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
seedrandom@2.4.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9A+PDmgm+2du77B5i0Ip2cxOqqHjgNxnBgglxLcX78A2D6c2rTo61z4jnVABpF4cKeDMDG+cmXXvdnqse2VqMA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
semver-compare@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YM3/ITh2MJ5MtzaM429anh+x2jiLVjqILF4m4oyQB18W7Ggea7BfqdH/wGMK7dDiMghv/6WG7znWMwUDzJiXow==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
semver@5.7.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cBznnQ9KjJqU67B52RMC65CMarK2600WFnbkcaiwWq3xy/5haFJlshgnpjovMVJ+Hff49d8GEn0b87C5pDQ10g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
semver@6.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BR7VvDCVHO+q2xBEWskxS6DJE1qRnb7DxzUrogb71CWoSficBxYsiAGd+Kl0mmq/MprG9yArRkyrQxTO6XjMzA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
semver@7.6.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oVekP1cKtI+CTDvHWYFUcMtsK/00wmAEfyqKfNdARm8u1wNVhSgaX7A8d4UuIlUI5e84iEwOhs7ZPYRmzU9U6A==}
engines: {node: '>=10'}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
hasBin: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sentence-case@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8LS0JInaQMCRoQ7YUytAo/xUu5W2XnQxV2HI/6uM6U7CITS1RqPElr30V6uIqyMKM9lJGRVFy5/4CuzcixNYSg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
serialize-error@7.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8I8TjW5KMOKsZQTvoxjuSIa7foAwPWGOts+6o7sgjz41/qMD9VQHEDxi6PBvK2l0MXUmqZyNpUK+T2tQaaElvw==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
set-function-length@1.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-j4t6ccc+VsKwYHso+kElc5neZpjtq9EnRICFZtWyBsLojhmeF/ZBd/elqm22WJh/BziDe/SBiOeAt0m2mfLD0g==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
set-function-name@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7PGFlmtwsEADb0WYyvCMa1t+yke6daIG4Wirafur5kcf+MhUnPms1UeR0CKQdTZD81yESwMHbtn+TR+dMviakQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
setprototypeof@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-E5LDX7Wrp85Kil5bhZv46j8jOeboKq5JMmYM3gVGdGH8xFpPWXUMsNrlODCrkoxMEeNi/XZIwuRvY4XNwYMJpw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sharp@0.31.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XcR4+FCLBFKw1bdB+GEhnUNXNXvnt0tDo4WsBsraKymuo/IAuPuCBVAL2wIkUw2r/dwFW5Q5+g66Kwl2dgDFVg==}
engines: {node: '>=14.15.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
shebang-command@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EV3L1+UQWGor21OmnvojK36mhg+TyIKDh3iFBKBohr5xeXIhNBcx8oWdgkTEEQ+BEFFYdLRuqMfd5L84N1V5Vg==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
shebang-command@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kHxr2zZpYtdmrN1qDjrrX/Z1rR1kG8Dx+gkpK1G4eXmvXswmcE1hTWBWYUzlraYw1/yZp6YuDY77YtvbN0dmDA==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
shebang-regex@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wpoSFAxys6b2a2wHZ1XpDSgD7N9iVjg29Ph9uV/uaP9Ex/KXlkTZTeddxDPSYQpgvzKLGJke2UU0AzoGCjNIvQ==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
shebang-regex@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7++dFhtcx3353uBaq8DDR4NuxBetBzC7ZQOhmTQInHEd6bSrXdiEyzCvG07Z44UYdLShWUyXt5M/yhz8ekcb1A==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
shell-quote@1.8.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6j1W9l1iAs/4xYBI1SYOVZyFcCis9b4KCLQ8fgAGG07QvzaRLVVRQvAy85yNmmZSjYjg4MWh4gNvlPujU/5LpA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
shiki-es@0.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RbRMD+IuJJseSZljDdne9ThrUYrwBwJR04FvN4VXpfsU3MNID5VJGHLAD5je/HGThCyEKNgH+nEkSFEWKD7C3Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: Please migrate to https://github.com/antfu/shikiji
shuffle-seed@1.1.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Vr9wlwMKJVUeFNGyc4aNbrzkI568gkve7ykyJ+1/cz78j3yRlJODWU0CuJ/fmk3MCjvAClpnqlycd/Y53UG3UA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
side-channel@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fDW/EZ6Q9RiO8eFG8Hj+7u/oW+XrPTIChwCOM2+th2A6OblDtYYIpve9m+KvI9Z4C9qSEXlaGR6bTEYHReuglA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
siginfo@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ybx0WO1/8bSBLEWXZvEd7gMW3Sn3JFlW3TvX1nREbDLRNQNaeNN8WK0meBwPdAaOI7TtRRRJn/Es1zhrrCHu7g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
signal-exit@4.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bzyZ1e88w9O1iNJbKnOlvYTrWPDl46O1bG0D3XInv+9tkPrxrN8jUUTiFlDkkmKWgn1M6CfIA13SuGqOa9Korw==}
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
simple-concat@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cSFtAPtRhljv69IK0hTVZQ+OfE9nePi/rtJmw5UjHeVyVroEqJXP1sFztKUy1qU+xvz3u/sfYJLa947b7nAN2Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
simple-get@4.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-brv7p5WgH0jmQJr1ZDDfKDOSeWWg+OVypG99A/5vYGPqJ6pxiaHLy8nxtFjBA7oMa01ebA9gfh1uMCFqOuXxvA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
simple-swizzle@0.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JA//kQgZtbuY83m+xT+tXJkmJncGMTFT+C+g2h2R9uxkYIrE2yy9sgmcLhCnw57/WSD+Eh3J97FPEDFnbXnDUg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
simple-update-notifier@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-a2B9Y0KlNXl9u/vsW6sTIu9vGEpfKu2wRV6l1H3XEas/0gUIzGzBoP/IouTcUQbm9JWZLH3COxyn03TYlFax6w==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sirv@2.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-94Bdh3cC2PKrbgSOUqTiGPWVZeSiXfKOVZNJniWoqrWrRkB1CJzBU3NEbiTsPcYy1lDsANA/THzS+9WBiy5nfQ==}
engines: {node: '>= 10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
sirv@3.0.0:
resolution: {integrity: sha512-BPwJGUeDaDCHihkORDchNyyTvWFhcusy1XMmhEVTQTwGeybFbp8YEmB+njbPnth1FibULBSBVwCQni25XlCUDg==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
slash@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3dOsAHXXUkQTpOYcoAxLIorMTp4gIQr5IW3iVb7A7lFIp0VHhnynm9izx6TssdrIcVIESAlVjtnO2K8bg+Coew==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
slashes@3.0.12:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Q9VME8WyGkc7pJf6QEkj3wE+2CnvZMI+XJhwdTPR8Z/kWQRXi7boAWLDibRPyHRTUTPx5FaU7MsyrjI3yLB4HA==}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
slice-ansi@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pSyv7bSTC7ig9Dcgbw9AuRNUb5k5V6oDudjZoMBSr13qpLBG7tB+zgCkARjq7xIUgdz5P1Qe8u+rSGdouOOIyQ==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
smart-buffer@4.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-94hK0Hh8rPqQl2xXc3HsaBoOXKV20MToPkcXvwbISWLEs+64sBq5kFgn2kJDHb1Pry9yrP0dxrCI9RRci7RXKg==}
engines: {node: '>= 6.0.0', npm: '>= 3.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
snake-case@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-LAOh4z89bGQvl9pFfNF8V146i7o7/CqFPbqzYgP+yYzDIDeS9HaNFtXABamRW+AQzEVODcvE79ljJ+8a9YSdMg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
source-map-js@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-itJW8lvSA0TXEphiRoawsCksnlf8SyvmFzIhltqAHluXd88pkCd+cXJVHTDwdCr0IzwptSm035IHQktUu1QUMg==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
source-map-support@0.5.21:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-uBHU3L3czsIyYXKX88fdrGovxdSCoTGDRZ6SYXtSRxLZUzHg5P/66Ht6uoUlHu9EZod+inXhKo3qQgwXUT/y1w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
source-map@0.6.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UjgapumWlbMhkBgzT7Ykc5YXUT46F0iKu8SGXq0bcwP5dz/h0Plj6enJqjz1Zbq2l5WaqYnrVbwWOWMyF3F47g==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
spdx-correct@3.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kN9dJbvnySHULIluDHy32WHRUu3Og7B9sbY7tsFLctQkIqnMh3hErYgdMjTYuqmcXX+lK5T1lnUt3G7zNswmZA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
spdx-exceptions@2.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PiU42r+xO4UbUS1buo3LPJkjlO7430Xn5SVAhdpzzsPHsjbYVflnnFdATgabnLude+Cqu25p6N+g2lw/PFsa4w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
spdx-expression-parse@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cbqHunsQWnJNE6KhVSMsMeH5H/L9EpymbzqTQ3uLwNCLZ1Q481oWaofqH7nO6V07xlXwY6PhQdQ2IedWx/ZK4Q==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
spdx-expression-parse@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Clya5JIij/7C6bRR22+tnGXbc4VKlibKSVj2iHvVeX5iMW7s1SIQlqu699JkODJJIhh/pUu8L0/VLh8xflD+LQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
spdx-license-ids@3.0.17:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sh8PWc/ftMqAAdFiBu6Fy6JUOYjqDJBJvIhpfDMyHrr0Rbp5liZqd4TjtQ/RgfLjKFZb+LMx5hpml5qOWy0qvg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
speakingurl@14.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1POYv7uv2gXoyGFpBCmpDVSNV74IfsWlDW216UPjbWufNf+bSU6GdbDsxdcxtfwb4xlI3yxzOTKClUosxARYrQ==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
spectorjs@0.9.30:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-I9/VI3gfO3UiBCUXj20lQjP3fbezP2y03Virnv3jcMpIiF+/NOyWDrBQ+U8vf29IXHPscxOXzzmZDCkETznsMg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sprintf-js@1.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-D9cPgkvLlV3t3IzL0D0YLvGA9Ahk4PcvVwUbN0dSGr1aP0Nrt4AEnTUbuGvquEC0mA64Gqt1fzirlRs5ibXx8g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sprintf-js@1.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Oo+0REFV59/rz3gfJNKQiBlwfHaSESl1pcGyABQsnnIfWOFt6JNj5gCog2U6MLZ//IGYD+nA8nI+mTShREReaA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sql-formatter@13.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/nZQXuN7KzipFNM20ko+dHY4kOr9rymSfZLUDED8rhx3m8OK5y74jcyN+y1L51ZqHqiB0kp40VdpZP99uWvQdA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
sshpk@1.18.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2p2KJZTSqQ/I3+HX42EpYOa2l3f8Erv8MWKsy2I9uf4wA7yFIkXRffYdsx86y6z4vHtV8u7g+pPlr8/4ouAxsQ==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
stackback@0.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1XMJE5fQo1jGH6Y/7ebnwPOBEkIEnT4QF32d5R1+VXdXveM0IBMJt8zfaxX1P3QhVwrYe+576+jkANtSS2mBbw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
stat-mode@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-jH9EhtKIjuXZ2cWxmXS8ZP80XyC3iasQxMDV8jzhNJpfDb7VbQLVW4Wvsxz9QZvzV+G4YoSfBUVKDOyxLzi/sg==}
engines: {node: '>= 6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
state-local@1.0.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HTEHMNieakEnoe33shBYcZ7NX83ACUjCu8c40iOGEZsngj9zRnkqS9j1pqQPXwobB0ZcVTk27REb7COQ0UR59w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
statuses@1.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-OpZ3zP+jT1PI7I8nemJX4AKmAX070ZkYPVWV/AaKTJl+tXCTGyVdC1a4SL8RUQYEwk/f34ZX8UTykN68FwrqAA==}
engines: {node: '>= 0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
statuses@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RwNA9Z/7PrK06rYLIzFMlaF+l73iwpzsqRIFgbMLbTcLD6cOao82TaWefPXQvB2fOC4AjuYSEndS7N/mTCbkdQ==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
std-env@3.7.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JPbdCEQLj1w5GilpiHAx3qJvFndqybBysA3qUOnznweH4QbNYUsW/ea8QzSrnh0vNsezMMw5bcVool8lM0gwzg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
stream-to-buffer@0.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Da4WoKaZyu3nf+bIdIifh7IPkFjARBnBK+pYqn0EUJqksjV9afojjaCCHUemH30Jmu7T2qcKvlZm2ykN38uzaw==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
stream-to@0.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Kg1BSDTwgGiVMtTCJNlo7kk/xzL33ZuZveEBRt6rXw+f1WLK/8kmz2NVCT/Qnv0JkV85JOHcLhD82mnXsR3kPw==}
engines: {node: '>= 0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strict-event-emitter-types@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Nk/brWYpD85WlOgzw5h173aci0Teyv8YdIAEtV+N88nDB0dLlazZyJMIsN6eo1/AR61l+p6CJTG1JIyFaoNEEA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string-length@5.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9Ep08KAMUn0OadnVaBuRdE2l615CQ508kr0XMadjClfYpdCyvrbFp6Taebo8yyxokQ4viUd/xPPUA4FGgUa0ow==}
engines: {node: '>=12.20'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string-width@4.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wKyQRQpjJ0sIp62ErSZdGsjMJWsap5oRNihHhu6G7JVO/9jIB6UyevL+tXuOqrng8j/cxKTWyWUwvSTriiZz/g==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string-width@5.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HnLOCR3vjcY8beoNLtcjZ5/nxn2afmME6lhrDrebokqMap+XbeW8n9TXpPDOqdGK5qcI3oT0GKTW6wC7EMiVqA==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string.prototype.matchall@4.0.11:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-NUdh0aDavY2og7IbBPenWqR9exH+E26Sv8e0/eTe1tltDGZL+GtBkDAnnyBtmekfK6/Dq3MkcGtzXFEd1LQrtg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string.prototype.padend@3.1.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XZpspuSB7vJWhvJc9DLSlrXl1mcA2BdoY5jjnS135ydXqLoqhs96JjDtCkjJEQHvfqZIp9hBuBMgI589peyx9Q==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
string.prototype.repeat@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0u/TldDbKD8bFCQ/4f5+mNRrXwZ8hg2w7ZR8wa16e8z9XpePWl3eGEcUD0OXpEH/VJH/2G3gjUtR3ZOiBe2S/w==}
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string.prototype.trim@1.2.9:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-klHuCNxiMZ8MlsOihJhJEBJAiMVqU3Z2nEXWfWnIqjN0gEFS9J9+IxKozWWtQGcgoa1WUZzLjKPTr4ZHNFTFxw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string.prototype.trimend@1.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-p73uL5VCHCO2BZZ6krwwQE3kCzM7NKmis8S//xEC6fQonchbum4eP6kR4DLEjQFO3Wnj3Fuo8NM0kOSjVdHjZQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string.prototype.trimstart@1.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UXSH262CSZY1tfu3G3Secr6uGLCFVPMhIqHjlgCUtCCcgihYc/xKs9djMTMUOb2j1mVSeU8EU6NWc/iQKU6Gfg==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string_decoder@1.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-n/ShnvDi6FHbbVfviro+WojiFzv+s8MPMHBczVePfUpDJLwoLT0ht1l4YwBCbi8pJAveEEdnkHyPyTP/mzRfwg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string_decoder@1.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-hkRX8U1WjJFd8LsDJ2yQ/wWWxaopEsABU1XfkM8A+j0+85JAGppt16cr1Whg6KIbb4okU6Mql6BOj+uup/wKeA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strip-ansi@6.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Y38VPSHcqkFrCpFnQ9vuSXmquuv5oXOKpGeT6aGrr3o3Gc9AlVa6JBfUSOCnbxGGZF+/0ooI7KrPuUSztUdU5A==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strip-ansi@7.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-iq6eVVI64nQQTRYq2KtEg2d2uU7LElhTJwsH4YzIHZshxlgZms/wIc4VoDQTlG/IvVIrBKG06CrZnp0qv7hkcQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strip-bom-string@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-uCC2VHvQRYu+lMh4My/sFNmF2klFymLX1wHJeXnbEJERpV/ZsVuonzerjfrGpIGF7LBVa1O7i9kjiWvJiFck8g==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strip-bom@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vavAMRXOgBVNF6nyEEmL3DBK19iRpDcoIwW+swQ+CbGiu7lju6t+JklA1MHweoWtadgt4ISVUsXLyDq34ddcwA==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strip-final-newline@3.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dOESqjYr96iWYylGObzd39EuNTa5VJxyvVAEm5Jnh7KGo75V43Hk1odPQkNDyXNmUR6k+gEiDVXnjB8HJ3crXw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strip-json-comments@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-4gB8na07fecVVkOI6Rs4e7T6NOTki5EmL7TUduTs6bu3EdnSycntVJ4re8kgZA+wx9IueI2Y11bfbgwtzuE0KQ==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strip-json-comments@3.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6fPc+R4ihwqP6N/aIv2f1gMH8lOVtWQHoqC4yK6oSDVVocumAsfCqjkXnqiYMhmMwS/mEHLp7Vehlt3ql6lEig==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strip-literal@2.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Op+UycaUt/8FbN/Z2TWPBLge3jWrP3xj10f3fnYxf052bKuS3EKs1ZQcVGjnEMdsNVAM+plXRdmjrZ/KgG3Skw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
style-mod@4.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-wnD1HyVqpJUI2+eKZ+eo1UwghftP6yuFheBqqe+bWCotBjC2K1YnteJILRMs3SM4V/0dLEW1SC27MWP5y+mwmw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sucrase@3.35.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8EbVDiu9iN/nESwxeSxDKe0dunta1GOlHufmSSXxMD2z2/tMZpDMpvXQGsc+ajGo8y2uYUmixaSRUc/QPoQ0GA==}
engines: {node: '>=16 || 14 >=14.17'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
sumchecker@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MvjXzkz/BOfyVDkG0oFOtBxHX2u3gKbMHIF/dXblZsgD3BWOFLmHovIpZY7BykJdAjcqRCBi1WYBNdEC9yI7vg==}
engines: {node: '>= 8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
superjson@2.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8iGv75BYOa0xRJHK5vRLEjE2H/i4lulTjzpUXic3Eg8akftYjkmQDa8JARQ42rlczXyFR3IeRoeFCc7RxHsYZA==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
supports-color@5.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QjVjwdXIt408MIiAqCX4oUKsgU2EqAGzs2Ppkm4aQYbjm+ZEWEcW4SfFNTr4uMNZma0ey4f5lgLrkB0aX0QMow==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
supports-color@7.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-qpCAvRl9stuOHveKsn7HncJRvv501qIacKzQlO/+Lwxc9+0q2wLyv4Dfvt80/DPn2pqOBsJdDiogXGR9+OvwRw==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
supports-preserve-symlinks-flag@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ot0WnXS9fgdkgIcePe6RHNk1WA8+muPa6cSjeR3V8K27q9BB1rTE3R1p7Hv0z1ZyAc8s6Vvv8DIyWf681MAt0w==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
svg-tags@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ovssysQTa+luh7A5Weu3Rta6FJlFBBbInjOh722LIt6klpU2/HtdUbszju/G4devcvk8PGt7FCLv5wftu3THUA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
symbol-tree@3.2.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9QNk5KwDF+Bvz+PyObkmSYjI5ksVUYtjW7AU22r2NKcfLJcXp96hkDWU3+XndOsUb+AQ9QhfzfCT2O+CNWT5Tw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
synckit@0.9.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7gr8p9TQP6RAHusBOSLs46F4564ZrjV8xFmw5zCmgmhGUcw2hxsShhJ6CEiHQMgPDwAQ1fWHPM0ypc4RMAig4A==}
engines: {node: ^14.18.0 || >=16.0.0}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tailwind-merge@2.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vkYrLpIP+lgR0tQCG6AP7zZXCTLc1Lnv/CCRT3BqJ9CZ3ui2++GPaGb1x/ILsINIMSYqqvrpqjUFsMNLlW99EA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tailwind-variants@0.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2xmhAf4UIc3PijOUcJPA1LP4AbxhpcHuHM2C26xM0k81r0maAO6uoUSHl3APmvHZcY5cZCY/bYuJdfFa4eGoaw==}
engines: {node: '>=16.x', pnpm: '>=7.x'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
tailwindcss: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tailwindcss-animate@1.0.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bl6mpH3T7I3UFxuvDEXLxy/VuFxBk5bbzplh7tXI68mwMokNYd1t9qPBHlnyTwfa4JGC4zP516I1hYYtQ/vspA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
tailwindcss: '>=3.0.0 || insiders'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tailwindcss-react-aria-components@1.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-j852nEhbvD7/zxpNI7hY+6mYm//2zSKuPPq3NNohMi+/nA0hxjaJGg0LYEPzumn/efNT0Itrq+/TMD+r/m1EqA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
tailwindcss: '>=3.0.0 || insiders'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tailwindcss@3.4.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZoyXOdJjISB7/BcLTR6SEsLgKtDStYyYZVLsUtWChO4Ps20CBad7lfJKVDiejocV4ME1hLmyY0WJE3hSDcmQ2A==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
tar-fs@2.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-V0r2Y9scmbDRLCNex/+hYzvp/zyYjvFbHPNgVTKfQvVrb6guiE/fxP+XblDNR011utopbkex2nM4dHNV6GDsng==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tar-stream@2.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ujeqbceABgwMZxEJnk2HDY2DlnUZ+9oEcb1KzTVfYHio0UE6dG71n60d8D2I4qNvleWrrXpmjpt7vZeF1LnMZQ==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tar@6.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DZ4yORTwrbTj/7MZYq2w+/ZFdI6OZ/f9SFHR+71gIVUZhOQPHzVCLpvRnPgyaMpfWxxk/4ONva3GQSyNIKRv6A==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
temp-file@3.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-C5tjlC/HCtVUOi3KWVokd4vHVViOmGjtLwIh4MuzPo/nMYTV/p1urt3RnMz2IWXDdKEGJH3k5+KPxtqRsUYGtg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
test-exclude@6.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cAGWPIyOHU6zlmg88jwm7VRyXnMN7iV68OGAbYDk/Mh/xC/pzVPlQtY6ngoIH/5/tciuhGfvESU8GrHrcxD56w==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
text-table@0.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-N+8UisAXDGk8PFXP4HAzVR9nbfmVJ3zYLAWiTIoqC5v5isinhr+r5uaO8+7r3BMfuNIufIsA7RdpVgacC2cSpw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
thenify-all@1.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RNxQH/qI8/t3thXJDwcstUO4zeqo64+Uy/+sNVRBx4Xn2OX+OZ9oP+iJnNFqplFra2ZUVeKCSa2oVWi3T4uVmA==}
engines: {node: '>=0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
thenify@3.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RVZSIV5IG10Hk3enotrhvz0T9em6cyHBLkH/YAZuKqd8hRkKhSfCGIcP2KUY0EPxndzANBmNllzWPwak+bheSw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tiny-invariant@1.3.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-+FbBPE1o9QAYvviau/qC5SE3caw21q3xkvWKBtja5vgqOWIHHJ3ioaq1VPfn/Szqctz2bU/oYeKd9/z5BL+PVg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tinybench@2.8.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1/eK7zUnIklz4JUUlL+658n58XO2hHLQfSk1Zf2LKieUjxidN16eKFEoDEfjHc3ohofSSqK3X5yO6VGb6iW8Lw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tinycolor2@1.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XPaBkWQJdsf3pLKJV9p4qN/S+fm2Oj8AIPo1BTUhg5oxkvm9+SVEGFdhyOz7tTdUTfvxMiAs4sp6/eZO2Ew+pw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tinypool@0.8.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-i11VH5gS6IFeLY3gMBQ00/MmLncVP7JLXOw1vlgkytLmJK7QnEr7NXf0LBdxfmNPAeyetukOk0bOYrJrFGjYJQ==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
tinyrainbow@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-weEDEq7Z5eTHPDh4xjX789+fHfF+P8boiFB+0vbWzpbnbsEr/GRaohi/uMKxg8RZMXnl1ItAi/IUHWMsjDV7kQ==}
engines: {node: '>=14.0.0'}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tinyspy@2.2.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KYad6Vy5VDWV4GH3fjpseMQ/XU2BhIYP7Vzd0LG44qRWm/Yt2WCOTicFdvmgo6gWaqooMQCawTtILVQJupKu7A==}
engines: {node: '>=14.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tmp-promise@3.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-RwM7MoPojPxsOBYnyd2hy0bxtIlVrihNs9pj5SUvY8Zz1sQcQG2tG1hSr8PDxfgEB8RNKDhqbIlroIarSNDNsQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tmp@0.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nZD7m9iCPC5g0pYmcaxogYKggSfLsdxl8of3Q/oIbqCqLLIO9IAF0GWjX1z9NZRHPiXv8Wex4yDCaZsgEw0Y8w==}
engines: {node: '>=14.14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
to-fast-properties@2.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/OaKK0xYrs3DmxRYqL/yDc+FxFUVYhDlXMhRmv3z915w2HF1tnN1omB354j8VUGO/hbRzyD6Y3sA7v7GS/ceog==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
to-ico@1.1.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-5kIh7m7bkIlqIESEZkL8gAMMzucXKfPe3hX2FoDY5HEAfD9OJU+Qh9b6Enp74w0qRcxVT5ejss66PHKqc3AVkg==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
to-regex-range@5.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-65P7iz6X5yEr1cwcgvQxbbIw7Uk3gOy5dIdtZ4rDveLqhrdJP+Li/Hx6tyK0NEb+2GCyneCMJiGqrADCSNk8sQ==}
engines: {node: '>=8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
toidentifier@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-o5sSPKEkg/DIQNmH43V0/uerLrpzVedkUh8tGNvaeXpfpuwjKenlSox/2O/BTlZUtEe+JG7s5YhEz608PlAHRA==}
engines: {node: '>=0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tosource@2.0.0-alpha.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KAB2lrSS48y91MzFPFuDg4hLbvDiyTjOVgaK7Erw+5AmZXNq4sFRVn8r6yxSLuNs15PaokrDRpS61ERY9uZOug==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
totalist@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-sf4i37nQ2LBx4m3wB74y+ubopq6W/dIzXg0FDGjsYnZHVa1Da8FH853wlL2gtUhg+xJXjfk3kUZS3BRoQeoQBQ==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tough-cookie@2.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nlLsUzgm1kfLXSXfRZMc1KLAugd4hqJHDTvc2hDIwS3mZAfMEuMbc03SujMF+GEcpaX/qboeycw6iO8JwVv2+g==}
engines: {node: '>=0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tough-cookie@4.1.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Loo5UUvLD9ScZ6jh8beX1T6sO1w2/MpCRpEP7V280GKMVUQ0Jzar2U3UJPsrdbziLEMMhu3Ujnq//rhiFuIeag==}
engines: {node: '>=6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tr46@0.0.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-N3WMsuqV66lT30CrXNbEjx4GEwlow3v6rr4mCcv6prnfwhS01rkgyFdjPNBYd9br7LpXV1+Emh01fHnq2Gdgrw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tr46@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tk2G5R2KRwBd+ZN0zaEXpmzdKyOYksXwywulIX95MBODjSzMIuQnQ3m8JxgbhnL1LeVo7lqQKsYa1O3Htl7K5g==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
truncate-utf8-bytes@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-95Pu1QXQvruGEhv62XCMO3Mm90GscOCClvrIUwCM0PYOXK3kaF3l3sIHxx71ThJfcbM2O5Au6SO3AWCSEfW4mQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ts-api-utils@1.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-UQMIo7pb8WRomKR1/+MFVLTroIvDVtMX3K6OUir8ynLyzB8Jeriont2bTAtmNPa1ekAgN7YPDyf6V+ygrdU+eQ==}
engines: {node: '>=16'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '>=4.2.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ts-interface-checker@0.1.13:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Y/arvbn+rrz3JCKl9C4kVNfTfSm2/mEp5FSz5EsZSANGPSlQrpRI5M4PKF+mJnE52jOO90PnPSc3Ur3bTQw0gA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ts-results@3.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-FWqxGX2NHp5oCyaMd96o2y2uMQmSu8Dey6kvyuFdRJ2AzfmWo3kWa4UsPlCGlfQ/qu03m09ZZtppMoY8EMHuiA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib@2.6.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-xNvxJEOUiWPGhUuUdQgAJPKOOJfGnIyKySOc09XkKsgdUV/3E2zvwZYdejjmRgPCgcym1juLH3226yA7sEFJKQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tsx@4.16.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-MPgN+CuY+4iKxGoJNPv+1pyo5YWZAQ5XfsyobUG+zoKG7IkvCPLZDEyoIb8yLS2FcWci1nlxAqmvPlFWD5AFiQ==}
engines: {node: '>=18.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
tunnel-agent@0.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-McnNiV1l8RYeY8tBgEpuodCC1mLUdbSN+CYBL7kJsJNInOP8UjDDEwdk6Mw60vdLLrr5NHKZhMAOSrR2NZuQ+w==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tweetnacl@0.14.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KXXFFdAbFXY4geFIwoyNK+f5Z1b7swfXABfL7HXCmoIWMKU3dmS26672A4EeQtDzLKy7SXmfBu51JolvEKwtGA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
type-check@0.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XleUoc9uwGXqjWwXaUTZAmzMcFZ5858QA2vvx1Ur5xIcixXIP+8LnFDgRplU30us6teqdlskFfu+ae4K79Ooew==}
engines: {node: '>= 0.8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
type-detect@4.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0fr/mIH1dlO+x7TlcMy+bIDqKPsw/70tVyeHW787goQjhmqaZe10uwLujubK9q9Lg6Fiho1KUKDYz0Z7k7g5/g==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
type-fest@0.13.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-34R7HTnG0XIJcBSn5XhDd7nNFPRcXYRZrBB2O2jdKqYODldSzBAqzsWoZYYvduky73toYS/ESqxPvkDf/F0XMg==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
type-fest@0.20.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Ne+eE4r0/iWnpAxD852z3A+N0Bt5RN//NjJwRd2VFHEmrywxf5vsZlh4R6lixl6B+wz/8d+maTSAkN1FIkI3LQ==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
type-is@1.6.18:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-TkRKr9sUTxEH8MdfuCSP7VizJyzRNMjj2J2do2Jr3Kym598JVdEksuzPQCnlFPW4ky9Q+iA+ma9BGm06XQBy8g==}
engines: {node: '>= 0.6'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
typed-array-buffer@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gEymJYKZtKXzzBzM4jqa9w6Q1Jjm7x2d+sh19AdsD4wqnMPDYyvwpsIc2Q/835kHuo3BEQ7CjelGhfTsoBb2MQ==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
typed-array-byte-length@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3iMJ9q0ao7WE9tWcaYKIptkNBuOIcZCCT0d4MRvuuH88fEoEH62IuQe0OtraD3ebQEoTRk8XCBoknUNc1Y67pw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
typed-array-byte-offset@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Ous0vodHa56FviZucS2E63zkgtgrACj7omjwd/8lTEMEPFFyjfixMZ1ZXenpgCFBBt4EC1J2XsyVS2gkG0eTFA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
typed-array-length@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/OxDN6OtAk5KBpGb28T+HZc2M+ADtvRxXrKKbUwtsLgdoxgX13hyy7ek6bFRl5+aBs2yZzB0c4CnQfAtVypW/g==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Metadata should not depend on absolute text spans (#11390) close #11304 Changelog: - update: add `ide.snapshot` optional metadata field containing the source code of the file - update: `syncFileContents` method tries to repair the metadata spans when it detects that the source file was edited and the received code does not match the code stored in the `ide.snapshot` metadata field # Important Notes Tested in gui
2024-10-28 12:41:46 +03:00
typescript-eslint@8.11.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-cBRGnW3FSlxaYwU8KfAewxFK5uzeOAp0l2KebIlPDOT5olVi65KDG/yjBooPBG0kGW/HLkoz1c/iuBFehcS3IA==}
engines: {node: ^18.18.0 || ^20.9.0 || >=21.1.0}
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '*'
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
peerDependenciesMeta:
typescript:
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
typescript@5.5.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/hreyEujaB0w76zKo6717l3L0o/qEUtRgdvUBvlkhoWeOVMjMuHNHk0BRBzikzuGDqNmPQbg5ifMEqsHLiIUcQ==}
engines: {node: '>=14.17'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
uc.micro@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8Y75pvTYkLJW2hWQHXxoqRgV7qb9B+9vFEtidML+7koHUFapnVJAZ6cKs+Qjz5Aw3aZWHMC6u0wJE3At+nSGwA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ufo@1.5.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Y7HYmWaFwPUmkoQCUIAYpKqkOf+SbVj/2fJJZ4RJMCfZp0rTGwRbzQD+HghfnhKOjL9E01okqz+ncJskGYfBNw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
unbox-primitive@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-61pPlCD9h51VoreyJ0BReideM3MDKMKnh6+V9L08331ipq6Q8OFXZYiqP6n/tbHx4s5I9uRhcye6BrbkizkBDw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
undici-types@5.26.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JlCMO+ehdEIKqlFxk6IfVoAUVmgz7cU7zD/h9XZ0qzeosSHmUJVOzSQvvYSYWXkFXC+IfLKSIffhv0sVZup6pA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
undici-types@6.19.8:
resolution: {integrity: sha512-ve2KP6f/JnbPBFyobGHuerC9g1FYGn/F8n1LWTwNxCEzd6IfqTwUQcNXgEtmmQ6DlRrC1hrSrBnCZPokRrDHjw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
unfetch@4.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-F9p7yYCn6cIW9El1zi0HI6vqpeIvBsr3dSuRO6Xuppb1u5rXpCPmMvLSyECLhybr9isec8Ohl0hPekMVrEinDA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
universal-cookie@4.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-lbRVHoOMtItjWbM7TwDLdl8wug7izB0tq3/YVKhT/ahB4VDvWMyvnADfnJI8y6fSvsjh51Ix7lTGC6Tn4rMPhw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
universalify@0.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rBJeI5CXAlmy1pV+617WB9J63U6XcazHHF2f2dbJix4XzpUF0RS3Zbj0FGIOCAva5P/d/GBOYaACQ1w+0azUkg==}
engines: {node: '>= 4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
universalify@0.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-CJ1QgKmNg3CwvAv/kOFmtnEN05f0D/cn9QntgNOQlQF9dgvVTHj3t+8JPdjqawCHk7V/KA+fbUqzZ9XWhcqPUg==}
engines: {node: '>= 4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
universalify@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gptHNQghINnc/vTGIk0SOFGFNXw7JVrlRUtConJRlvaw6DuX0wO5Jeko9sWrMBhh+PsYAZ7oXAiOnf/UKogyiw==}
engines: {node: '>= 10.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
unpipe@1.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pjy2bYhSsufwWlKwPc+l3cN7+wuJlK6uz0YdJEOlQDbl6jo/YlPi4mb8agUkVC8BF7V8NuzeyPNqRksA3hztKQ==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
upath@2.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1uEe95xksV1O0CYKXo8vQvN1JEbtJp7lb7C5U9HMsIp6IVwntkH/oNUzyVNQSd4S1sYk2FpSSW44FqMc8qee5w==}
engines: {node: '>=4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
update-browserslist-db@1.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EdRAaAyk2cUE1wOf2DkEhzxqOQvFOoRJFNS6NeyJ01Gp2beMRpBAINjM2iDXE3KCuKhwnvHIQCJm6ThL2Z+HzQ==}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
hasBin: true
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
browserslist: '>= 4.21.0'
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
upper-case-first@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-514ppYHBaKwfJRK/pNC6c/OxfGa0obSnAl106u97Ed0I625Nin96KAjttZF6ZL3e1XLtphxnqrOi9iWgm+u+bg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
upper-case@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-KgdgDGJt2TpuwBUIjgG6lzw2GWFRCW9Qkfkiv0DxqHHLYJHmtmdUIKcZd8rHgFSjopVTlw6ggzCm1b8MFQwikg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
uri-js@4.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7rKUyy33Q1yc98pQ1DAmLtwX109F7TIfWlW1Ydo8Wl1ii1SeHieeh0HHfPeL2fMXK6z0s8ecKs9frCuLJvndBg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
url-parse@1.5.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-WypcfiRhfeUP9vvF0j6rw0J3hrWrw6iZv3+22h6iRMJ/8z1Tj6XfLP4DsUix5MhMPnXpiHDoKyoZ/bdCkwBCiQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
url-regex@3.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dQ9cJzMou5OKr6ZzfvwJkCq3rC72PNXhqz0v3EIhF4a3Np+ujr100AhUx2cKx5ei3iymoJpJrPB3sVSEMdqAeg==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
url@0.11.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kbailJa29QrtXnxgq+DdCEGlbTeYM2eJUxsz6vjZavrCYPMIFHMKQmSKYAIuUK2i7hgPm28a8piX5NTUtM/LKQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
url@0.11.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6hxOLGfZASQK/cijlZnZJTq8OXAkt/3YGfQX45vvMYXpZoo8NdWZcY73K108Jf759lS1Bv/8wXnHDTSz17dSRw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
use-sync-external-store@1.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-eEgnFxGQ1Ife9bzYs6VLi8/4X6CObHMw9Qr9tPY43iKwsPw8xE8+EFsf/2cFZ5S3esXgpWgtSCtLNS41F+sKPA==}
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0 || ^18.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
use-sync-external-store@1.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PElTlVMwpblvbNqQ82d2n6RjStvdSoNe9FG28kNfz3WiXilJm4DdNkEzRhCZuIDwY8U08WVihhGR5iRqAwfDiw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
react: ^16.8.0 || ^17.0.0 || ^18.0.0
utf8-byte-length@1.0.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Xn0w3MtiQ6zoz2vFyUVruaCL53O/DwUvkEeOvj+uulMm0BkUGYWmBYVyElqZaSLhY6ZD0ulfU3aBra2aVT4xfA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
util-deprecate@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EPD5q1uXyFxJpCrLnCc1nHnq3gOa6DZBocAIiI2TaSCA7VCJ1UJDMagCzIkXNsUYfD1daK//LTEQ8xiIbrHtcw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
utils-merge@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-pMZTvIkT1d+TFGvDOqodOclx0QWkkgi6Tdoa8gC8ffGAAqz9pzPTZWAybbsHHoED/ztMtkv/VoYTYyShUn81hA==}
engines: {node: '>= 0.4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
uuid@3.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HjSDRw6gZE5JMggctHBcjVak08+KEVhSIiDzFnT9S9aegmp85S/bReBVTb4QTFaRNptJ9kuYaNhnbNEOkbKb/A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
deprecated: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.
hasBin: true
validate-npm-package-license@3.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-DpKm2Ui/xN7/HQKCtpZxoRWBhZ9Z0kqtygG8XCgNQ8ZlDnxuQmWhj566j8fN4Cu3/JmbhsDo7fcAJq4s9h27Ew==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
validator@13.12.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-c1Q0mCiPlgdTVVVIJIrBuxNicYE+t/7oKeI9MWLj3fh/uq2Pxh/3eeWbVZ4OcGW1TUf53At0njHw5SMdA3tmMg==}
engines: {node: '>= 0.10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vary@1.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BNGbWLfd0eUPabhkXUVm0j8uuvREyTh5ovRa/dyow/BqAbZJyC+5fU+IzQOzmAKzYqYRAISoRhdQr3eIZ/PXqg==}
engines: {node: '>= 0.8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
veaury@2.4.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-E5VA0aFSk5brksOOS/rUkt3mYeDmLYTDQRWCwvRi3U+s9RN3EzJIZbXGr1K4/mla4YZ3HmZ0chZ3LEBPlOB7IA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
react: '>= 16.4.0'
react-dom: '>= 16.4.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
verror@1.10.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZZKSmDAEFOijERBLkmYfJ+vmk3w+7hOLYDNkRCuRuMJGEmqYNCNLyBBFwWKVMhfwaEF3WOd0Zlw86U/WC/+nYw==}
engines: {'0': node >=0.6.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
verror@1.10.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-veufcmxri4e3XSrT0xwfUR7kguIkaxBeosDg00yDWhk49wdwkSUrvvsm7nc75e1PUyvIeZj6nS8VQRYz2/S4Xg==}
engines: {node: '>=0.6.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vite-hot-client@0.2.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rOGAV7rUlUHX89fP2p2v0A2WWvV3QMX2UYq0fRqsWSvFvev4atHWqjwGoKaZT1VTKyLGk533ecu3eyd0o59CAg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vite: ^2.6.0 || ^3.0.0 || ^4.0.0 || ^5.0.0-0
vite-node@0.34.7:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0Yzb96QzHmqIKIs/x2q/sqG750V/EF6yDkS2p1WjJc1W2bgRSuQjf5vB9HY8h2nVb5j4pO5paS5Npcv3s69YUg==}
engines: {node: '>=v14.18.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
vite-node@1.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-de6HJgzC+TFzOu0NTC4RAIsyf/DY/ibWDYQUcuEA84EMHhcefTUGkjFHKKEJhQN4A+6I0u++kr3l36ZF2d7XRw==}
engines: {node: ^18.0.0 || >=20.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
vite-node@2.0.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZpJVkxcakYtig5iakNeL7N3trufe3M6vGuzYAr4GsbCTwobDeyPJpE4cjDhhPluv8OvQCFzu2LWp6GkoKRITXA==}
engines: {node: ^18.0.0 || >=20.0.0}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
hasBin: true
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
vite-plugin-inspect@0.8.7:
resolution: {integrity: sha512-/XXou3MVc13A5O9/2Nd6xczjrUwt7ZyI9h8pTnUMkr5SshLcb0PJUOVq2V+XVkdeU4njsqAtmK87THZuO2coGA==}
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
engines: {node: '>=14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nuxt/kit': '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vite: ^3.1.0 || ^4.0.0 || ^5.0.0-0
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nuxt/kit':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
vite-plugin-vue-devtools@7.6.3:
resolution: {integrity: sha512-p1rZMKzreWqxj9U05RaxY1vDoOhGYhA6iX8vKfo4nD6jqTmVoGjjk+U1g5HYwwTCdr/eck3kzO2f4gnPCjqVKA==}
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
engines: {node: '>=v14.21.3'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vite: ^3.1.0 || ^4.0.0-0 || ^5.0.0-0
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
vite-plugin-vue-inspector@5.2.0:
resolution: {integrity: sha512-wWxyb9XAtaIvV/Lr7cqB1HIzmHZFVUJsTNm3yAxkS87dgh/Ky4qr2wDEWNxF23fdhVa3jQ8MZREpr4XyiuaRqA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vite: ^3.0.0-0 || ^4.0.0-0 || ^5.0.0-0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
vite-plugin-wasm@3.3.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tVhz6w+W9MVsOCHzxo6SSMSswCeIw4HTrXEi6qL3IRzATl83jl09JVO1djBqPSwfjgnpVHNLYcaMbaDX5WB/pg==}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
peerDependencies:
vite: ^2 || ^3 || ^4 || ^5
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
vite@5.4.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1hvaPshuPUtxeQ0hsVH3Mud0ZanOLwVTneA1EgbAM5LhaZEqyPWGRQ7BtaMvUrTDeEaC8pxtj6a6jku3x4z6SQ==}
engines: {node: ^18.0.0 || >=20.0.0}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
hasBin: true
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node': ^18.0.0 || >=20.0.0
less: '*'
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
lightningcss: ^1.21.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
sass: '*'
sass-embedded: '*'
stylus: '*'
sugarss: '*'
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
terser: ^5.4.0
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
less:
optional: true
lightningcss:
optional: true
sass:
optional: true
sass-embedded:
optional: true
stylus:
optional: true
sugarss:
optional: true
terser:
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vitest@1.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-H5r/dN06swuFnzNFhq/dnz37bPXnq8xB2xB5JOVk8K09rUtoeNN+LHWkoQ0A/i3hvbUKKcCei9KpbxqHMLhLLA==}
engines: {node: ^18.0.0 || >=20.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@edge-runtime/vm': '*'
'@types/node': ^18.0.0 || >=20.0.0
'@vitest/browser': 1.6.0
'@vitest/ui': 1.6.0
happy-dom: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsdom: ^24.1.0
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@edge-runtime/vm':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/browser':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/ui':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
happy-dom:
optional: true
jsdom:
optional: true
vscode-uri@3.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AyFQ0EVmsOZOlAnxoFOGOq1SQDWAB7C6aqMGS23svWAllfOaxbuFvcT8D1i8z3Gyn8fraVeZNNmN6e9bxxXkKw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Table Editor Widget (#10774) Fixes #10293 The Table Editor Widget allows adding rows and columns, editing cells and renaming columns. [Screencast from 2024-08-07 13-17-37.webm](https://github.com/user-attachments/assets/d2e708b5-6516-4107-bc17-f018e455c111) # Important Notes * The parts of Table Visualization which were useful for the widget were put in vue component. On this occasion, we use aggrid vue.
2024-08-12 17:45:58 +03:00
vue-component-type-helpers@2.0.29:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-58i+ZhUAUpwQ+9h5Hck0D+jr1qbYl4voRt5KffBx8qzELViQ4XdT/Tuo+mzq8u63teAG8K0lLaOiL5ofqW38rg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
vue-demi@0.14.10:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-nMZBOwuzabUO0nLgIcc6rycZEebF6eeUfaiQx9+WSk8e29IbLvPU9feI6tqW4kTo3hvoYAJkMh8n8D0fuISphg==}
engines: {node: '>=12'}
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
hasBin: true
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/composition-api': ^1.0.0-rc.1
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
vue: ^3.0.0-0 || ^2.6.0
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/composition-api':
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vue-eslint-parser@9.4.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2rYRLWlIpaiN8xbPiDyXZXRgLGOtWxERV7ND5fFAv5qo1D2N9Fu9MNajBNc6o13lZ+24DAWCkQCvj4klgmcITg==}
engines: {node: ^14.17.0 || >=16.0.0}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
eslint: '>=6.0.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vue-react-wrapper@0.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-kvG3A+fua1GkSiwO24Dp/i67KTz1yTH55HjxVmfnKtVA91sWoAlx2MZ728ooV4PKDt7LCapyPdJesoylPmHkUg==}
engines: {pnpm: '>=7'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vue: ^3
vue-resize@2.0.0-alpha.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-7+iqOueLU7uc9NrMfrzbG8hwMqchfVfSzpVlCMeJQe4pyibqyoifDNbKTZvwxZKDvGkB+PdFeKvnGZMoEb8esg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
vue: ^3.0.0
vue-template-compiler@2.7.16:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-AYbUWAJHLGGQM7+cNTELw+KsOG9nl2CnSv467WobS5Cv9uk3wFcnr1Etsz2sEIHEZvw1U+o9mRlEO6QbZvUPGQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vue-tsc@2.0.24:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1qi4P8L7yS78A7OJ7CDDxUIZPD6nVxoQEgX3DkRZNi1HI1qOfzOJwQlNpmwkogSVD6S/XcanbW9sktzpSxz6rA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '>=5.0.0'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue@3.5.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-w1YB4lAwC9ByH6AnFY0JvZF+y70Usul9jDfKIKtM5xA97q/JPS5R7mqq0fhA6D2PQxYPZdgb5jzFKLyOga5pnw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
typescript: '*'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
typescript:
optional: true
w3c-keyname@2.2.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-dpojBhNsCNN7T82Tm7k26A6G9ML3NkhDsnw9n/eoxSRlVBB4CEtIQ/KTCLI2Fwf3ataSXRhYFkQi3SlnFwPvPQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
w3c-xmlserializer@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-o8qghlI8NZHU1lLPrpi2+Uq7abh4GGPpYANlalzWxyWteJOCsr/P+oPBA49TOLu5FTZO4d3F9MnWJfiMo4BkmA==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
webidl-conversions@3.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-2JAn3z8AR6rjK8Sm8orRC0h/bcl/DqL7tRPdGZ4I1CjdF+EaMLmYxBHyXuKL849eucPFhvBoxMsflfOb8kxaeQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
webidl-conversions@7.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-VwddBukDzu71offAQR975unBIGqfKZpM+8ZX6ySk8nYhVoo5CYaZyzt3YBvYtRtO+aoGlqxPg/B87NGVZ/fu6g==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
whatwg-encoding@3.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6qN4hJdMwfYBtE3YBTTHhoeuUrDBPZmbQaxWAqSALV/MeEnR5z1xd8UKud2RAkFoPkmB+hli1TZSnyi84xz1vQ==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
whatwg-fetch@3.6.20:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EqhiFU6daOA8kpjOWTL0olhVOF3i7OrFzSYiGsEMB8GcXS+RrzauAERX65xMeNWVqxA6HXH2m69Z9LaKKdisfg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
whatwg-mimetype@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-QaKxh0eNIi2mE9p2vEdzfagOKHCcj1pJ56EEHGQOVxp8r9/iszLUUV7v89x9O1p/T+NlTM5W7jW6+cz4Fq1YVg==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
whatwg-url@14.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1lfMEm2IEr7RIV+f4lUNPOqfFL+pO+Xw3fJSqmjX9AbXcXcYOkCe1P6+9VBZB6n94af16NfZf+sSk0JCBZC9aw==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
whatwg-url@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-saE57nupxk6v3HY35+jzBwYa0rKSy0XR8JSxZPwgLr7ys0IBzhGviA1/TUGJLmSVqs8pb9AnvICXEuOHLprYTw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
which-boxed-primitive@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-bwZdv0AKLpplFY2KZRX6TvyuN7ojjr7lwkg6ml0roIy9YeuSr7JS372qlNW18UQYzgYK9ziGcerWqZOmEn9VNg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
which-builtin-type@1.1.3:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YmjsSMDBYsM1CaFiayOVT06+KJeXf0o5M/CAd4o1lTadFAtacTUM49zoYxr/oroopFDfhvN6iEcBxUyc3gvKmw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
which-collection@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-K4jVyjnBdgvc86Y6BkaLZEN933SwYOuBFkdmBu9ZfkcAbdVbpITnDmjvZ/aQjRXQrv5EPkTnD1s39GiiqbngCw==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
which-typed-array@1.1.15:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-oV0jmFtUky6CXfkqehVvBP/LSWJ2sy4vWMioiENyJLePrBO/yKyV9OyJySfAKosh+RYkIl5zJCNZ8/4JncrpdA==}
engines: {node: '>= 0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
which@1.3.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-HxJdYWq1MTIQbJ3nw0cqssHoTNU267KlrDuGZ1WYlxDStUtKUhOaJmh112/TZmHxxUfuJqPXSOm7tDyas0OSIQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
which@2.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BLI3Tl1TW3Pvl70l3yq3Y64i+awpwXqsGBYWkkqMtnbXgrMD+yj7rhW0kuEDxzJaYXGjEW5ogapKNMEKNMjibA==}
engines: {node: '>= 8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
why-is-node-running@2.2.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6tSwToZxTOcotxHeA+qGCq1mVzKR3CwcJGmVcY+QE8SHy6TnpFnh8PAvPNHYr7EcuVeG0QSMxtYCuO1ta/G/oA==}
engines: {node: '>=8'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
word-wrap@1.2.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-BN22B5eaMMI9UMtjrGd5g5eCYPpCPDUy0FJXbYsaT5zYxjFOckS53SQDE3pWkVoWpHXVb3BrYcEN4Twa55B5cA==}
engines: {node: '>=0.10.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
wrap-ansi@7.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-YVGIj2kamLSTxw6NsZjoBxfSwsn0ycdesmc4p+Q21c5zPuZ1pl+NfxVdxPtdHvmNVOQ6XSYG4AUtyt/Fi7D16Q==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
wrap-ansi@8.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-si7QWI6zUMq56bESFvagtmzMdGOtoxfR+Sez11Mobfc7tm+VkUckk9bW2UeffTGVUbOksxmSw0AA2gs8g71NCQ==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
wrappy@1.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-l4Sp/DRseor9wL6EvV2+TuQn63dMkPjZ/sp9XkghTEbV9KlPS1xUsZ3u7/IQO4wxtcFB4bgpQPRcR3QCvezPcQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws@8.18.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-8VbfWfHLbbwu3+N6OKsOMpBdT4kXPDDB9cJk2bJ6mh9ucxdlnNvH1e+roYkKmN9Nxw2yjz7VzeO9oOz2zJ04Pw==}
engines: {node: '>=10.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
bufferutil: ^4.0.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
utf-8-validate: '>=5.0.2'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependenciesMeta:
bufferutil:
optional: true
utf-8-validate:
optional: true
xhr@2.6.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/eCGLb5rxjx5e3mF1A7s+pLlR6CGyqWN91fv1JgER5mVWg1MZmlhBvy9kjcsOdRk8RrIujotWyJamfyrp+WIcA==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xml-name-validator@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ICP2e+jsHvAj2E2lIHxa5tjXRlKDJo4IdvPvCXbXQGdzSfmSpNVyIKMvoZHjDY9DP0zV17iI85o90vRFXNccRw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xml-name-validator@5.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-EvGK8EJ3DhaHfbRlETOWAS5pO9MZITeauHKJyb8wyajUfQUenkIg2MvLDTZ4T/TgIcm3HU0TFBgWWboAZ30UHg==}
engines: {node: '>=18'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xml-parse-from-string@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ErcKwJTF54uRzzNMXq2X5sMIy88zJvfN2DmdoQvy7PAFJ+tPRU6ydWuOKNMyfmOjdyBQTFREi60s0Y0SyI0G0g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xml2js@0.5.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-drPFnkQJik/O+uPKpqSgr22mpuFHqKdbS835iAQrUC73L2F5WkboIRd63ai/2Yg6I1jzifPFKH2NTK+cfglkIA==}
engines: {node: '>=4.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xmlbuilder@11.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-fDlsI/kFEx7gLvbecc0/ohLG50fugQp8ryHzMTuW9vSa1GJ0XYWKnhsUx7oie3G98+r56aTQIUB4kht42R3JvA==}
engines: {node: '>=4.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xmlbuilder@15.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-yMqGBqtXyeN1e3TGYvgNgDVZ3j84W4cwkOXQswghol6APgZWaff9lnbvN7MHYJOiXsvGPXtjTYJEiC9J2wv9Eg==}
engines: {node: '>=8.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xmlchars@2.2.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-JZnDKK8B0RCDw84FNdDAIpZK+JuJw+s7Lz8nksI7SIuU3UXJJslUthsi+uWBUYOwPFwW7W7PRLRfUKpxjtjFCw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xtend@4.0.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-LKYU1iAXJXUgAXn9URjiu+MWhyUXHsvfp7mcuYm9dSUKK0/CjtrUwFAxD82/mCWbtLsGjFIad0wIsod4zrTAEQ==}
engines: {node: '>=0.4'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
y-leveldb@0.1.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-6ulEn5AXfXJYi89rXPEg2mMHAyyw8+ZfeMMdOtBbV8FJpQ1NOrcgi6DTAcXof0dap84NjHPT2+9d0rb6cFsjEg==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
yjs: ^13.0.0
y-protocols@1.0.6:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-vHRF2L6iT3rwj1jub/K5tYcTT/mEYDUppgNPXwp8fmLpui9f7Yeq3OEtTLVF012j39QnV+KEQpNqoN7CWU7Y9Q==}
engines: {node: '>=16.0.0', npm: '>=8.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
yjs: ^13.0.0
y-textarea@1.0.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-gvU/BzKq+4ivm2Fbl7u4vno39xGyet/CK4KdQ/Kf1c5GQ+Obq80UgAuUDR9knx4U3SH5aiyobT0xrSHeoBDCAw==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
peerDependencies:
yjs: ^13.5.27
y-websocket@1.5.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-Y3021uy0anOIHqAPyAZbNDoR05JuMEGjRNI8c+K9MHzVS8dWoImdJUjccljAznc8H2L7WkIXhRHZ1igWNRSgPw==}
engines: {node: '>=16.0.0', npm: '>=8.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
peerDependencies:
yjs: ^13.5.6
y18n@5.0.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-0pfFzegeDWJHJIAmTLRP2DwHjdF5s7jo9tuztdQxAhINCdvS+3nGINqPd00AphqJR/0LhANUS6/+7SCb98YOfA==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yallist@3.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-a4UGQaWPH59mOXUYnAG2ewncQS4i4F43Tv3JoAM+s2VDAmS9NsK8GpDMLrCHPksFT7h3K6TOoUNn2pb7RoXx4g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yallist@4.0.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-3wdGidZyq5PB084XLES5TpOSRA3wjXAlIWMhum2kRcv/41Sn2emQ0dycQW4uZXLejwKvg6EsvbdlVL+FYEct7A==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yaml@2.4.5:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-aBx2bnqDzVOyNKfsysjA2ms5ZlnjSAW2eG3/L5G/CSujfjLJTJsEw1bGw8kCf04KodQWk1pxlGnZ56CRxiawmg==}
engines: {node: '>= 14'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hasBin: true
yargs-parser@21.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-tVpsJW7DdjecAiFpbIB1e3qxIQsE6NoPc5/eTdrbbIC4h0LVsWhnoa3g+m2HclBIujHzsxZ4VJVA+GUuc2/LBw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yargs@17.6.2:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-1/9UrdHjDZc0eOU0HxOHoS78C69UD3JRMvzlJ7S79S2nTaWRA/whGCTV8o9e/N/1Va9YIV7Q4sOxD8VV4pCWOw==}
engines: {node: '>=12'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yauzl@2.10.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-p4a9I6X6nu6IhoGmBqAcbJy1mlC4j27vEPZX9F4L4/vZT3Lyq1VkFHw/V/PUcB9Buo+DG3iHkT0x3Qya58zc3g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yjs@13.6.18:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-GBTjO4QCmv2HFKFkYIJl7U77hIB1o22vSCSQD1Ge8ZxWbIbn8AltI4gyXbtL+g5/GJep67HCMq3Y5AmNwDSyEg==}
engines: {node: '>=16.0.0', npm: '>=8.0.0'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yocto-queue@0.1.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-rVksvsnNCdJ/ohGc6xgPwyN8eheCxsiLM8mxuE/t/mOVqJewPuO1miLpTHQiRgTKCLexL4MeAFVagts7HmNZ2Q==}
engines: {node: '>=10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
yocto-queue@1.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-b4JR1PFR10y1mKjhHY9LaGo6tmrgjit7hxVIeAmyMw3jegXR4dhYqLaQF5zMXZxY7tLpMyJeLjr1C4rLmkVe8g==}
engines: {node: '>=12.20'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
zen-observable-ts@0.8.19:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-u1a2rpE13G+jSzrg3aiCqXU5tN2kw41b+cBZGmnc+30YimdkKiDj9bTowcB41eL77/17RF/h+393AuVgShyheQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
zen-observable@0.8.15:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-PQ2PC7R9rslx84ndNBZB/Dkv8V8fZEpk83RLgXtYd0fwUgEjseMn1Dgajh2x6S8QbZAFa9p2qVCEuYZNgve0dQ==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
zip-stream@4.1.1:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-9qv4rlDiopXg4E69k+vMHjNN63YFMe9sZMrdlvKnCjlCRWeCBswPPMPUfx+ipsAWq1LXHe70RcbaHdJJpS6hyQ==}
engines: {node: '>= 10'}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
zod-validation-error@3.4.0:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-ZOPR9SVY6Pb2qqO5XHt+MkkTRxGXb4EVtnjc9JpXUOtUB1T9Ru7mZOT361AN3MsetVe7R0a1KZshJDZdgp9miQ==}
engines: {node: '>=18.0.0'}
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
peerDependencies:
zod: ^3.18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
zod@3.23.8:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-XBx9AXhXktjUqnepgTiE5flcKIYWi/rme0Eaj+5Y0lftuGBq+jyRu/md4WnuxqgP1ubdpNCsYEYPxrzVHD8d6g==}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
zustand@4.5.4:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
resolution: {integrity: sha512-/BPMyLKJPtFEvVL0E9E9BTUM63MNyhPGlvxk1XjrfWTUlV+BR8jufjsovHzrtR6YNcBEcL7cMHovL1n9xHawEg==}
engines: {node: '>=12.7.0'}
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
peerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react': ^18.0.27
immer: '>=9.0.6'
react: '>=16.8'
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
peerDependenciesMeta:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react':
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
optional: true
immer:
optional: true
react:
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
snapshots:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
7zip-bin@5.2.0: {}
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/client-side-row-model@31.3.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/core': 31.3.4
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
tslib: 2.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/core@31.3.4':
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
dependencies:
tslib: 2.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/styles@31.3.4': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-enterprise/core@31.3.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/core': 31.3.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-enterprise/range-selection@31.3.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ag-grid-community/core': 31.3.4
'@ag-grid-enterprise/core': 31.3.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@akryum/tinypool@0.3.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@alloc/quick-lru@5.2.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ampproject/remapping@2.3.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/gen-mapping': 0.3.5
'@jridgewell/trace-mapping': 0.3.25
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@antfu/utils@0.7.10': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-amplify/auth@5.6.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-amplify/core': 5.8.5
'@aws-crypto/sha256-js': 5.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
amazon-cognito-identity-js: 6.3.6
buffer: 4.9.2
tslib: 2.6.3
url: 0.11.0
transitivePeerDependencies:
- encoding
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-amplify/core@5.8.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/sha256-js': 1.2.2
'@aws-sdk/client-cloudwatch-logs': 3.6.1
'@aws-sdk/types': 3.6.1
'@aws-sdk/util-hex-encoding': 3.6.1
'@types/node-fetch': 2.6.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isomorphic-unfetch: 3.1.0
tslib: 2.6.3
universal-cookie: 4.0.4
zen-observable-ts: 0.8.19
transitivePeerDependencies:
- encoding
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/ie11-detection@1.0.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/sha256-browser@1.2.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/ie11-detection': 1.0.0
'@aws-crypto/sha256-js': 1.2.2
'@aws-crypto/supports-web-crypto': 1.0.0
'@aws-crypto/util': 1.2.2
'@aws-sdk/types': 3.598.0
'@aws-sdk/util-locate-window': 3.568.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/sha256-js@1.2.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/util': 1.2.2
'@aws-sdk/types': 3.598.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/sha256-js@5.2.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/util': 5.2.0
'@aws-sdk/types': 3.598.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/supports-web-crypto@1.0.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/util@1.2.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.598.0
'@aws-sdk/util-utf8-browser': 3.259.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/util@5.2.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.598.0
'@smithy/util-utf8': 2.3.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/abort-controller@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/client-cloudwatch-logs@3.6.1':
dependencies:
'@aws-crypto/sha256-browser': 1.2.2
'@aws-crypto/sha256-js': 1.2.2
'@aws-sdk/config-resolver': 3.6.1
'@aws-sdk/credential-provider-node': 3.6.1
'@aws-sdk/fetch-http-handler': 3.6.1
'@aws-sdk/hash-node': 3.6.1
'@aws-sdk/invalid-dependency': 3.6.1
'@aws-sdk/middleware-content-length': 3.6.1
'@aws-sdk/middleware-host-header': 3.6.1
'@aws-sdk/middleware-logger': 3.6.1
'@aws-sdk/middleware-retry': 3.6.1
'@aws-sdk/middleware-serde': 3.6.1
'@aws-sdk/middleware-signing': 3.6.1
'@aws-sdk/middleware-stack': 3.6.1
'@aws-sdk/middleware-user-agent': 3.6.1
'@aws-sdk/node-config-provider': 3.6.1
'@aws-sdk/node-http-handler': 3.6.1
'@aws-sdk/protocol-http': 3.6.1
'@aws-sdk/smithy-client': 3.6.1
'@aws-sdk/types': 3.6.1
'@aws-sdk/url-parser': 3.6.1
'@aws-sdk/url-parser-native': 3.6.1
'@aws-sdk/util-base64-browser': 3.6.1
'@aws-sdk/util-base64-node': 3.6.1
'@aws-sdk/util-body-length-browser': 3.6.1
'@aws-sdk/util-body-length-node': 3.6.1
'@aws-sdk/util-user-agent-browser': 3.6.1
'@aws-sdk/util-user-agent-node': 3.6.1
'@aws-sdk/util-utf8-browser': 3.6.1
'@aws-sdk/util-utf8-node': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/config-resolver@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/signature-v4': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/credential-provider-env@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/property-provider': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/credential-provider-imds@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/property-provider': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/credential-provider-ini@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/property-provider': 3.6.1
'@aws-sdk/shared-ini-file-loader': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/credential-provider-node@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/credential-provider-env': 3.6.1
'@aws-sdk/credential-provider-imds': 3.6.1
'@aws-sdk/credential-provider-ini': 3.6.1
'@aws-sdk/credential-provider-process': 3.6.1
'@aws-sdk/property-provider': 3.6.1
'@aws-sdk/shared-ini-file-loader': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/credential-provider-process@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/credential-provider-ini': 3.6.1
'@aws-sdk/property-provider': 3.6.1
'@aws-sdk/shared-ini-file-loader': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/fetch-http-handler@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/protocol-http': 3.6.1
'@aws-sdk/querystring-builder': 3.6.1
'@aws-sdk/types': 3.6.1
'@aws-sdk/util-base64-browser': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/hash-node@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
'@aws-sdk/util-buffer-from': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/invalid-dependency@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/is-array-buffer@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-content-length@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/protocol-http': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-host-header@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/protocol-http': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-logger@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-retry@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/protocol-http': 3.6.1
'@aws-sdk/service-error-classification': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
uuid: 3.4.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-serde@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-signing@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/protocol-http': 3.6.1
'@aws-sdk/signature-v4': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-stack@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-user-agent@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/protocol-http': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/node-config-provider@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/property-provider': 3.6.1
'@aws-sdk/shared-ini-file-loader': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/node-http-handler@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/abort-controller': 3.6.1
'@aws-sdk/protocol-http': 3.6.1
'@aws-sdk/querystring-builder': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/property-provider@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/protocol-http@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/querystring-builder@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
'@aws-sdk/util-uri-escape': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/querystring-parser@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/service-error-classification@3.6.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/shared-ini-file-loader@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/signature-v4@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/is-array-buffer': 3.6.1
'@aws-sdk/types': 3.6.1
'@aws-sdk/util-hex-encoding': 3.6.1
'@aws-sdk/util-uri-escape': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/smithy-client@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/middleware-stack': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types@3.598.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@smithy/types': 3.3.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types@3.6.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/url-parser-native@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/querystring-parser': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
url: 0.11.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/url-parser@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/querystring-parser': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-base64-browser@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-base64-node@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-buffer-from': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-body-length-browser@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-body-length-node@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-buffer-from@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/is-array-buffer': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-hex-encoding@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-locate-window@3.568.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-uri-escape@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-user-agent-browser@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bowser: 2.11.0
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-user-agent-node@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/node-config-provider': 3.6.1
'@aws-sdk/types': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-utf8-browser@3.259.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-utf8-browser@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-utf8-node@3.6.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-sdk/util-buffer-from': 3.6.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/code-frame@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/highlight': 7.24.7
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/compat-data@7.25.4': {}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core@7.25.2':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ampproject/remapping': 2.3.0
'@babel/code-frame': 7.24.7
'@babel/generator': 7.25.6
'@babel/helper-compilation-targets': 7.25.2
'@babel/helper-module-transforms': 7.25.2(@babel/core@7.25.2)
'@babel/helpers': 7.25.6
'@babel/parser': 7.25.6
'@babel/template': 7.25.0
'@babel/traverse': 7.25.6
'@babel/types': 7.25.6
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
convert-source-map: 2.0.0
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
debug: 4.3.7
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
gensync: 1.0.0-beta.2
json5: 2.2.3
semver: 6.3.1
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/generator@7.25.6':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
'@jridgewell/gen-mapping': 0.3.5
'@jridgewell/trace-mapping': 0.3.25
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
jsesc: 2.5.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-annotate-as-pure@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-compilation-targets@7.25.2':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/compat-data': 7.25.4
'@babel/helper-validator-option': 7.24.8
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
browserslist: 4.23.3
lru-cache: 5.1.1
semver: 6.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-create-class-features-plugin@7.24.7(@babel/core@7.25.2)':
dependencies:
'@babel/core': 7.25.2
'@babel/helper-annotate-as-pure': 7.24.7
'@babel/helper-environment-visitor': 7.24.7
'@babel/helper-function-name': 7.24.7
'@babel/helper-member-expression-to-functions': 7.24.7
'@babel/helper-optimise-call-expression': 7.24.7
'@babel/helper-replace-supers': 7.24.7(@babel/core@7.25.2)
'@babel/helper-skip-transparent-expression-wrappers': 7.24.7
'@babel/helper-split-export-declaration': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
semver: 6.3.1
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-environment-visitor@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-function-name@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/template': 7.25.0
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-member-expression-to-functions@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/traverse': 7.25.6
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-module-imports@7.22.15':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-module-imports@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/traverse': 7.25.6
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-module-transforms@7.25.2(@babel/core@7.25.2)':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-module-imports': 7.24.7
'@babel/helper-simple-access': 7.24.7
'@babel/helper-validator-identifier': 7.24.7
'@babel/traverse': 7.25.6
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-optimise-call-expression@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-plugin-utils@7.24.7': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-replace-supers@7.24.7(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-environment-visitor': 7.24.7
'@babel/helper-member-expression-to-functions': 7.24.7
'@babel/helper-optimise-call-expression': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-simple-access@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/traverse': 7.25.6
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-skip-transparent-expression-wrappers@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/traverse': 7.25.6
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-split-export-declaration@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-string-parser@7.24.8': {}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-validator-identifier@7.24.7': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-validator-option@7.24.8': {}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helpers@7.25.6':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/template': 7.25.0
'@babel/types': 7.25.6
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/highlight@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-validator-identifier': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chalk: 2.4.2
js-tokens: 4.0.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/parser@7.25.6':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-proposal-decorators@7.24.7(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-create-class-features-plugin': 7.24.7(@babel/core@7.25.2)
'@babel/helper-plugin-utils': 7.24.7
'@babel/plugin-syntax-decorators': 7.24.7(@babel/core@7.25.2)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-proposal-private-methods@7.18.6(@babel/core@7.25.2)':
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-create-class-features-plugin': 7.24.7(@babel/core@7.25.2)
'@babel/helper-plugin-utils': 7.24.7
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-syntax-decorators@7.24.7(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-plugin-utils': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-syntax-import-attributes@7.24.7(@babel/core@7.25.2)':
Setup Screen Improvements (#10844)
2024-09-05 19:11:02 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-plugin-utils': 7.24.7
Setup Screen Improvements (#10844)
2024-09-05 19:11:02 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-syntax-import-meta@7.10.4(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-plugin-utils': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-syntax-jsx@7.24.7(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-plugin-utils': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-syntax-typescript@7.24.7(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-plugin-utils': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-transform-react-jsx-self@7.24.7(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-plugin-utils': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-transform-react-jsx-source@7.24.7(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-plugin-utils': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/plugin-transform-typescript@7.24.7(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/helper-annotate-as-pure': 7.24.7
'@babel/helper-create-class-features-plugin': 7.24.7(@babel/core@7.25.2)
'@babel/helper-plugin-utils': 7.24.7
'@babel/plugin-syntax-typescript': 7.24.7(@babel/core@7.25.2)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/runtime@7.24.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
regenerator-runtime: 0.14.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/template@7.25.0':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/code-frame': 7.24.7
'@babel/parser': 7.25.6
'@babel/types': 7.25.6
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/traverse@7.25.6':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/code-frame': 7.24.7
'@babel/generator': 7.25.6
'@babel/parser': 7.25.6
'@babel/template': 7.25.0
'@babel/types': 7.25.6
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
debug: 4.3.7
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
globals: 11.12.0
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types@7.25.6':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-string-parser': 7.24.8
'@babel/helper-validator-identifier': 7.24.7
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
to-fast-properties: 2.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@bcoe/v8-coverage@0.2.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/autocomplete@6.16.3(@codemirror/language@6.10.2)(@codemirror/state@6.4.1)(@codemirror/view@6.28.3)(@lezer/common@1.2.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/language': 6.10.2
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
'@lezer/common': 1.2.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/commands@6.6.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/language': 6.10.2
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
'@lezer/common': 1.2.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/lang-css@6.3.0(@codemirror/view@6.28.3)':
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/autocomplete': 6.16.3(@codemirror/language@6.10.2)(@codemirror/state@6.4.1)(@codemirror/view@6.28.3)(@lezer/common@1.2.1)
'@codemirror/language': 6.10.2
'@codemirror/state': 6.4.1
'@lezer/common': 1.2.1
'@lezer/css': 1.1.9
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@codemirror/view'
'@codemirror/lang-html@6.4.9':
dependencies:
'@codemirror/autocomplete': 6.16.3(@codemirror/language@6.10.2)(@codemirror/state@6.4.1)(@codemirror/view@6.28.3)(@lezer/common@1.2.1)
'@codemirror/lang-css': 6.3.0(@codemirror/view@6.28.3)
'@codemirror/lang-javascript': 6.2.2
'@codemirror/language': 6.10.2
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
'@lezer/common': 1.2.1
'@lezer/css': 1.1.9
'@lezer/html': 1.3.10
'@codemirror/lang-javascript@6.2.2':
dependencies:
'@codemirror/autocomplete': 6.16.3(@codemirror/language@6.10.2)(@codemirror/state@6.4.1)(@codemirror/view@6.28.3)(@lezer/common@1.2.1)
'@codemirror/language': 6.10.2
'@codemirror/lint': 6.8.1
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
'@lezer/common': 1.2.1
'@lezer/javascript': 1.4.18
'@codemirror/lang-json@6.0.1':
dependencies:
'@codemirror/language': 6.10.2
'@lezer/json': 1.0.2
'@codemirror/lang-markdown@6.3.0':
dependencies:
'@codemirror/autocomplete': 6.16.3(@codemirror/language@6.10.2)(@codemirror/state@6.4.1)(@codemirror/view@6.28.3)(@lezer/common@1.2.1)
'@codemirror/lang-html': 6.4.9
'@codemirror/language': 6.10.2
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
'@lezer/common': 1.2.1
'@lezer/markdown': 1.3.1
'@codemirror/language@6.10.2':
dependencies:
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
'@lezer/common': 1.2.1
'@lezer/highlight': 1.2.0
'@lezer/lr': 1.4.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
style-mod: 4.1.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/lint@6.8.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
crelt: 1.0.6
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/search@6.5.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
crelt: 1.0.6
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/state@6.4.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/theme-one-dark@6.1.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/language': 6.10.2
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
'@lezer/highlight': 1.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/view@6.28.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/state': 6.4.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
style-mod: 4.1.2
w3c-keyname: 2.2.8
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@csstools/selector-resolve-nested@1.1.0(postcss-selector-parser@6.1.0)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
postcss-selector-parser: 6.1.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@csstools/selector-specificity@3.1.1(postcss-selector-parser@6.1.0)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
postcss-selector-parser: 6.1.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@danmarshall/deckgl-typings@4.9.28':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/hammerjs': 2.0.45
'@types/react': 18.3.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
indefinitely-typed: 1.1.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@develar/schema-utils@2.6.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
ajv: 6.12.6
ajv-keywords: 3.5.2(ajv@6.12.6)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/asar@3.2.10':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
commander: 5.1.0
glob: 7.2.3
minimatch: 3.1.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/get@2.0.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
env-paths: 2.2.1
fs-extra: 8.1.0
got: 11.8.6
progress: 2.0.3
semver: 6.3.1
sumchecker: 3.0.1
optionalDependencies:
global-agent: 3.0.0
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/notarize@2.1.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra: 9.1.0
promise-retry: 2.0.1
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/notarize@2.2.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra: 9.1.0
promise-retry: 2.0.1
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/osx-sign@1.0.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
compare-version: 0.1.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra: 10.1.0
isbinaryfile: 4.0.10
minimist: 1.2.8
plist: 3.1.0
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/universal@1.5.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/asar': 3.2.10
'@malept/cross-spawn-promise': 1.1.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dir-compare: 3.3.0
fs-extra: 9.1.0
minimatch: 3.1.2
plist: 3.1.0
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@emotion/is-prop-valid@1.3.0':
Setup Screen Improvements (#10844)
2024-09-05 19:11:02 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@emotion/memoize': 0.9.0
Setup Screen Improvements (#10844)
2024-09-05 19:11:02 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@emotion/memoize@0.9.0':
Setup Screen Improvements (#10844)
2024-09-05 19:11:02 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@es-joy/jsdoccomment@0.49.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
comment-parser: 1.4.1
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esquery: 1.6.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
jsdoc-type-pratt-parser: 4.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/aix-ppc64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/aix-ppc64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-arm64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-arm64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-arm@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-arm@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-x64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/android-x64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/darwin-arm64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/darwin-arm64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/darwin-x64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/darwin-x64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/freebsd-arm64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/freebsd-arm64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/freebsd-x64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/freebsd-x64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-arm64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-arm64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-arm@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-arm@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-ia32@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-ia32@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-loong64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-loong64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-mips64el@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-mips64el@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-ppc64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-ppc64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-riscv64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-riscv64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-s390x@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-s390x@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-x64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/linux-x64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/netbsd-x64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/netbsd-x64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/openbsd-arm64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/openbsd-x64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/openbsd-x64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/sunos-x64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/sunos-x64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-arm64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-arm64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-ia32@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-ia32@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-x64@0.21.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/win32-x64@0.23.0':
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint-community/eslint-utils@4.4.0(eslint@9.13.0(jiti@1.21.6))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
eslint-visitor-keys: 3.4.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint-community/regexpp@4.11.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint/config-array@0.18.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint/object-schema': 2.1.4
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minimatch: 3.1.2
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint/core@0.7.0': {}
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint/eslintrc@3.1.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
ajv: 6.12.6
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
espree: 10.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
globals: 14.0.0
ignore: 5.3.1
import-fresh: 3.3.0
js-yaml: 4.1.0
minimatch: 3.1.2
strip-json-comments: 3.1.1
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint/js@9.13.0': {}
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint/object-schema@2.1.4': {}
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint/plugin-kit@0.2.1':
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
dependencies:
levn: 0.4.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@fal-works/esbuild-plugin-global-externals@2.1.2': {}
Add compression to the metadata code snapshot (#11470) close #11420 Changelog: - update: add zlib compression to the `snapshot` metadata field - add: implement nodejs `zlib` for polyglot ydoc-server - add: implement nodejs `Buffer` for polyglot ydoc-server
2024-11-05 14:57:43 +03:00
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@fast-check/vitest@0.0.8(vitest@1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
fast-check: 3.19.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vitest: 1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/core@1.6.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/utils': 0.2.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/dom@1.1.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/core': 1.6.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/dom@1.6.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/core': 1.6.4
'@floating-ui/utils': 0.2.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/utils@0.2.4': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/vue@1.1.0(vue@3.5.2(typescript@5.5.3))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/dom': 1.6.7
'@floating-ui/utils': 0.2.4
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
vue-demi: 0.14.10(vue@3.5.2(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@vue/composition-api'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- vue
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/ecma402-abstract@2.0.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/intl-localematcher': 0.5.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/fast-memoize@2.2.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/icu-messageformat-parser@2.7.8':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/ecma402-abstract': 2.0.0
'@formatjs/icu-skeleton-parser': 1.8.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/icu-skeleton-parser@1.8.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/ecma402-abstract': 2.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/intl-localematcher@0.5.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@histoire/app@0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@histoire/controls': 0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
'@histoire/shared': 0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/vendors': 0.17.17
'@types/flexsearch': 0.7.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
flexsearch: 0.7.21
shiki-es: 0.2.0
transitivePeerDependencies:
- vite
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@histoire/controls@0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))':
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
dependencies:
'@codemirror/commands': 6.6.0
'@codemirror/lang-json': 6.0.1
'@codemirror/language': 6.10.2
'@codemirror/lint': 6.8.1
'@codemirror/state': 6.4.1
'@codemirror/theme-one-dark': 6.1.2
'@codemirror/view': 6.28.3
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@histoire/shared': 0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/vendors': 0.17.17
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- vite
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@histoire/plugin-vue@0.17.17(histoire@0.17.17(@types/node@22.9.0)(lightningcss@1.25.1)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)))(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))(vue@3.5.2(typescript@5.5.3))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@histoire/controls': 0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
'@histoire/shared': 0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/vendors': 0.17.17
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
change-case: 4.1.2
globby: 13.2.2
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
histoire: 0.17.17(@types/node@22.9.0)(lightningcss@1.25.1)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
launch-editor: 2.8.0
pathe: 1.1.2
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- vite
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@histoire/shared@0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/vendors': 0.17.17
'@types/fs-extra': 9.0.13
'@types/markdown-it': 12.2.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chokidar: 3.6.0
pathe: 1.1.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/vendors@0.17.17': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@hookform/resolvers@3.6.0(react-hook-form@7.52.0(react@18.3.1))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
react-hook-form: 7.52.0(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@humanfs/core@0.19.0': {}
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@humanfs/node@0.16.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@humanfs/core': 0.19.0
'@humanwhocodes/retry': 0.3.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@humanwhocodes/module-importer@1.0.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@humanwhocodes/retry@0.3.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ianvs/prettier-plugin-sort-imports@4.3.0(prettier@3.3.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/generator': 7.25.6
'@babel/parser': 7.25.6
'@babel/traverse': 7.25.6
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prettier: 3.3.2
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Edit prettier config (#10648)
2024-07-24 11:47:05 +03:00
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date@3.5.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/message@3.1.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
intl-messageformat: 10.5.14
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/number@3.5.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/string@3.2.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@isaacs/cliui@8.0.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
string-width: 5.1.2
string-width-cjs: string-width@4.2.3
strip-ansi: 7.1.0
strip-ansi-cjs: strip-ansi@6.0.1
wrap-ansi: 8.1.0
wrap-ansi-cjs: wrap-ansi@7.0.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@istanbuljs/schema@0.1.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jest/schemas@29.6.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sinclair/typebox': 0.27.8
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/gen-mapping@0.3.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/set-array': 1.2.1
'@jridgewell/sourcemap-codec': 1.5.0
'@jridgewell/trace-mapping': 0.3.25
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/resolve-uri@3.1.2': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/set-array@1.2.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/sourcemap-codec@1.5.0': {}
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/trace-mapping@0.3.25':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/resolve-uri': 3.1.2
'@jridgewell/sourcemap-codec': 1.5.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@json-schema-spec/json-pointer@0.1.2': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@json-schema-tools/dereferencer@1.6.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@json-schema-tools/reference-resolver': 1.2.6
'@json-schema-tools/traverse': 1.10.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fast-safe-stringify: 2.1.1
transitivePeerDependencies:
- encoding
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@json-schema-tools/meta-schema@1.7.5': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@json-schema-tools/reference-resolver@1.2.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@json-schema-spec/json-pointer': 0.1.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isomorphic-fetch: 3.0.0
transitivePeerDependencies:
- encoding
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@json-schema-tools/traverse@1.10.4': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/clipboard@0.16.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/html': 0.16.0
'@lexical/list': 0.16.0
'@lexical/selection': 0.16.0
'@lexical/utils': 0.16.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/html@0.16.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/selection': 0.16.0
'@lexical/utils': 0.16.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/link@0.16.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/utils': 0.16.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/list@0.16.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/utils': 0.16.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/plain-text@0.16.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/clipboard': 0.16.0
'@lexical/selection': 0.16.0
'@lexical/utils': 0.16.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/selection@0.16.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
lexical: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/table@0.16.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/utils': 0.16.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/utils@0.16.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lexical/list': 0.16.0
'@lexical/selection': 0.16.0
'@lexical/table': 0.16.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lexical: 0.16.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common@1.2.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/css@1.1.9':
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common': 1.2.1
'@lezer/highlight': 1.2.0
'@lezer/lr': 1.4.1
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/highlight@1.2.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common': 1.2.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/html@1.3.10':
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common': 1.2.1
'@lezer/highlight': 1.2.0
'@lezer/lr': 1.4.1
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/javascript@1.4.18':
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common': 1.2.1
'@lezer/highlight': 1.2.0
'@lezer/lr': 1.4.1
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/json@1.0.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common': 1.2.1
'@lezer/highlight': 1.2.0
'@lezer/lr': 1.4.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/lr@1.4.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common': 1.2.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/markdown@1.3.1':
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@lezer/common': 1.2.1
'@lezer/highlight': 1.2.0
New markdown editor (#11469) Implements #11240. https://github.com/user-attachments/assets/4d2f8021-3e0f-4d39-95df-bcd72bf7545b # Important Notes - Fix a Yjs document corruption bug caused by `DeepReadonly` being replaced by a stub; introduce a `DeepReadonly` implementation without Vue dependency. - Fix right panel sizing when code editor is open. - Fix right panel slide-in animation. - `Ast.Function` renamed to `Ast.FunctionDef`.
2024-11-06 19:54:32 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@malept/cross-spawn-promise@1.1.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
cross-spawn: 7.0.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@malept/flatpak-bundler@0.4.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra: 9.1.0
lodash: 4.17.21
tmp-promise: 3.0.3
transitivePeerDependencies:
- supports-color
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@modyfi/vite-plugin-yaml@1.1.0(rollup@4.24.0)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/pluginutils': 5.1.0(rollup@4.24.0)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
js-yaml: 4.1.0
tosource: 2.0.0-alpha.3
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- rollup
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@monaco-editor/loader@1.4.0(monaco-editor@0.48.0)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
monaco-editor: 0.48.0
state-local: 1.0.7
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@monaco-editor/react@4.6.0(monaco-editor@0.48.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@monaco-editor/loader': 1.4.0(monaco-editor@0.48.0)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
monaco-editor: 0.48.0
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@noble/hashes@1.4.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nodelib/fs.scandir@2.1.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nodelib/fs.stat': 2.0.5
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
run-parallel: 1.2.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nodelib/fs.stat@2.0.5': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nodelib/fs.walk@1.2.8':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nodelib/fs.scandir': 2.1.5
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fastq: 1.17.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@one-ini/wasm@0.1.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@open-rpc/client-js@1.8.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
events: 3.3.0
isomorphic-fetch: 3.0.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
isomorphic-ws: 5.0.0(ws@8.18.0)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
strict-event-emitter-types: 2.0.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws: 8.18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- bufferutil
- encoding
- utf-8-validate
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@open-rpc/meta-schema@1.14.9': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@open-rpc/schema-utils-js@2.0.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@json-schema-tools/dereferencer': 1.6.3
'@json-schema-tools/meta-schema': 1.7.5
'@json-schema-tools/reference-resolver': 1.2.6
'@open-rpc/meta-schema': 1.14.9
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ajv: 6.12.6
detect-node: 2.1.0
fast-safe-stringify: 2.1.1
fs-extra: 10.1.0
is-url: 1.2.4
isomorphic-fetch: 3.0.0
transitivePeerDependencies:
- encoding
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@open-rpc/server-js@1.9.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@open-rpc/schema-utils-js': 2.0.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
body-parser: 1.20.2
connect: 3.7.0
cors: 2.8.5
json-schema-faker: 0.5.6
lodash: 4.17.21
node-ipc: 9.1.1
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws: 8.18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- bufferutil
- encoding
- supports-color
- utf-8-validate
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@pkgjs/parseargs@0.11.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@pkgr/core@0.1.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@playwright/test@1.45.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
playwright: 1.45.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@polka/url@1.0.0-next.25': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/breadcrumbs@3.5.16(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/link': 3.7.4(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/breadcrumbs': 3.7.7(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/button@3.9.8(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/toggle': 3.7.7(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/calendar@3.5.11(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@internationalized/date': 3.5.5
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/live-announcer': 3.3.4
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/calendar': 3.5.4(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/calendar': 3.4.9(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/checkbox@3.14.6(react@18.3.1)':
dependencies:
'@react-aria/form': 3.0.8(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/toggle': 3.10.7(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/checkbox': 3.6.8(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/toggle': 3.7.7(react@18.3.1)
'@react-types/checkbox': 3.8.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/collections@3.0.0-alpha.4(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/ssr': 3.9.6(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
use-sync-external-store: 1.2.2(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/color@3.0.0-rc.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/numberfield': 3.11.6(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/slider': 3.7.11(react@18.3.1)
'@react-aria/spinbutton': 3.6.8(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/textfield': 3.14.8(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-aria/visually-hidden': 3.8.15(react@18.3.1)
'@react-stately/color': 3.7.2(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-types/color': 3.0.0-rc.1(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/combobox@3.10.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/listbox': 3.13.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/live-announcer': 3.3.4
'@react-aria/menu': 3.15.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/overlays': 3.23.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/textfield': 3.14.8(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/combobox': 3.9.2(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/combobox': 3.12.1(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/datepicker@3.11.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@internationalized/date': 3.5.5
'@internationalized/number': 3.5.3
'@internationalized/string': 3.2.3
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/form': 3.0.8(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/spinbutton': 3.6.8(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/datepicker': 3.10.2(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/calendar': 3.4.9(react@18.3.1)
'@react-types/datepicker': 3.8.2(react@18.3.1)
'@react-types/dialog': 3.5.12(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/dialog@3.5.17(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/overlays': 3.23.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/dialog': 3.5.12(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/dnd@3.7.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@internationalized/string': 3.2.3
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/live-announcer': 3.3.4
'@react-aria/overlays': 3.23.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/dnd': 3.4.2(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus@3.18.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
clsx: 2.1.1
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/form@3.0.8(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/grid@3.10.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/live-announcer': 3.3.4
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/grid': 3.9.2(react@18.3.1)
'@react-stately/selection': 3.16.2(react@18.3.1)
'@react-types/checkbox': 3.8.3(react@18.3.1)
'@react-types/grid': 3.2.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/gridlist@3.9.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/grid': 3.10.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/list': 3.10.8(react@18.3.1)
'@react-stately/tree': 3.8.4(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/i18n@3.12.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date': 3.5.5
'@internationalized/message': 3.1.4
'@internationalized/number': 3.5.3
'@internationalized/string': 3.2.3
'@react-aria/ssr': 3.9.6(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/interactions@3.22.3(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/ssr': 3.9.6(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/label@3.7.11(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/link@3.7.4(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/link': 3.5.7(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/listbox@3.13.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/list': 3.10.8(react@18.3.1)
'@react-types/listbox': 3.5.1(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/live-announcer@3.3.4':
dependencies:
'@swc/helpers': 0.5.12
'@react-aria/menu@3.15.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/overlays': 3.23.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/menu': 3.8.2(react@18.3.1)
'@react-stately/tree': 3.8.4(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/menu': 3.9.11(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/meter@3.4.16(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/progress': 3.4.16(react@18.3.1)
'@react-types/meter': 3.4.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/numberfield@3.11.6(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/spinbutton': 3.6.8(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/textfield': 3.14.8(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/numberfield': 3.9.6(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/numberfield': 3.8.5(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/overlays@3.23.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/ssr': 3.9.6(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-aria/visually-hidden': 3.8.15(react@18.3.1)
'@react-stately/overlays': 3.6.10(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/overlays': 3.8.9(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/progress@3.4.16(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/progress': 3.5.6(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/radio@3.10.7(react@18.3.1)':
dependencies:
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/form': 3.0.8(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/radio': 3.10.7(react@18.3.1)
'@react-types/radio': 3.8.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/searchfield@3.7.8(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/textfield': 3.14.8(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/searchfield': 3.5.6(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/searchfield': 3.5.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/select@3.14.9(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/form': 3.0.8(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/listbox': 3.13.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/menu': 3.15.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-aria/visually-hidden': 3.8.15(react@18.3.1)
'@react-stately/select': 3.6.7(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/select': 3.9.6(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/selection@3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/selection': 3.16.2(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/separator@3.4.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/slider@3.7.11(react@18.3.1)':
dependencies:
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/slider': 3.5.7(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/slider': 3.7.5(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/spinbutton@3.6.8(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/live-announcer': 3.3.4
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/ssr@3.9.6(react@18.3.1)':
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@swc/helpers': 0.5.12
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/switch@3.6.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/toggle': 3.10.7(react@18.3.1)
'@react-stately/toggle': 3.7.7(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/switch': 3.5.5(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/table@3.15.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/grid': 3.10.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/live-announcer': 3.3.4
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-aria/visually-hidden': 3.8.15(react@18.3.1)
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/flags': 3.0.3
'@react-stately/table': 3.12.2(react@18.3.1)
'@react-types/checkbox': 3.8.3(react@18.3.1)
'@react-types/grid': 3.2.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/table': 3.10.1(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/tabs@3.9.5(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/tabs': 3.6.9(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/tabs': 3.3.9(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/tag@3.4.5(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
dependencies:
'@react-aria/gridlist': 3.9.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/list': 3.10.8(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/textfield@3.14.8(react@18.3.1)':
dependencies:
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/form': 3.0.8(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/textfield': 3.9.6(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/toggle@3.10.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/toggle': 3.7.7(react@18.3.1)
'@react-types/checkbox': 3.8.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/toolbar@3.0.0-beta.8(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/tooltip@3.7.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/tooltip': 3.4.12(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/tooltip': 3.4.11(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/tree@3.0.0-alpha.5(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/gridlist': 3.9.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/tree': 3.8.4(react@18.3.1)
'@react-types/button': 3.9.6(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/utils@3.25.3(react@18.3.1)':
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/ssr': 3.9.6(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
clsx: 2.1.1
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/virtualizer@4.0.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-stately/virtualizer': 4.0.2(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/visually-hidden@3.8.15(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/calendar@3.5.4(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date': 3.5.5
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/calendar': 3.4.9(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/checkbox@3.6.8(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/checkbox': 3.8.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/collections@3.10.9(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/color@3.7.2(react@18.3.1)':
dependencies:
'@internationalized/number': 3.5.3
'@internationalized/string': 3.2.3
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/numberfield': 3.9.6(react@18.3.1)
'@react-stately/slider': 3.5.7(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/color': 3.0.0-rc.1(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/combobox@3.9.2(react@18.3.1)':
dependencies:
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/list': 3.10.8(react@18.3.1)
'@react-stately/overlays': 3.6.10(react@18.3.1)
'@react-stately/select': 3.6.7(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/combobox': 3.12.1(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/data@3.11.6(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/datepicker@3.10.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date': 3.5.5
'@internationalized/string': 3.2.3
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/overlays': 3.6.10(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/datepicker': 3.8.2(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/dnd@3.4.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/selection': 3.16.2(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/flags@3.0.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/form@3.0.5(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/grid@3.9.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/selection': 3.16.2(react@18.3.1)
'@react-types/grid': 3.2.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/layout@4.0.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/table': 3.12.2(react@18.3.1)
'@react-stately/virtualizer': 4.0.2(react@18.3.1)
'@react-types/grid': 3.2.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/table': 3.10.1(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/list@3.10.8(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/selection': 3.16.2(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/menu@3.8.2(react@18.3.1)':
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/overlays': 3.6.10(react@18.3.1)
'@react-types/menu': 3.9.11(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/numberfield@3.9.6(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/number': 3.5.3
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/numberfield': 3.8.5(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/overlays@3.6.10(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/overlays': 3.8.9(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/radio@3.10.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/radio': 3.8.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/searchfield@3.5.6(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/searchfield': 3.5.8(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/select@3.6.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/list': 3.10.8(react@18.3.1)
'@react-stately/overlays': 3.6.10(react@18.3.1)
'@react-types/select': 3.9.6(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/selection@3.16.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/slider@3.5.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/slider': 3.7.5(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/table@3.12.2(react@18.3.1)':
dependencies:
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/flags': 3.0.3
'@react-stately/grid': 3.9.2(react@18.3.1)
'@react-stately/selection': 3.16.2(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/grid': 3.2.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/table': 3.10.1(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/tabs@3.6.9(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/list': 3.10.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/tabs': 3.3.9(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/toggle@3.7.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/checkbox': 3.8.3(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/tooltip@3.4.12(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/overlays': 3.6.10(react@18.3.1)
'@react-types/tooltip': 3.4.11(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/tree@3.8.4(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/selection': 3.16.2(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/utils@3.10.4(react@18.3.1)':
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@swc/helpers': 0.5.12
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/virtualizer@4.0.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/breadcrumbs@3.7.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/link': 3.5.7(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/button@3.9.6(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/calendar@3.4.9(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date': 3.5.5
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/checkbox@3.8.3(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/color@3.0.0-rc.1(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/slider': 3.7.5(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/combobox@3.12.1(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/datepicker@3.8.2(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date': 3.5.5
'@react-types/calendar': 3.4.9(react@18.3.1)
'@react-types/overlays': 3.8.9(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/dialog@3.5.12(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/overlays': 3.8.9(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/form@3.7.6(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/grid@3.2.8(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/link@3.5.7(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/listbox@3.5.1(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/menu@3.9.11(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/overlays': 3.8.9(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/meter@3.4.3(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/progress': 3.5.6(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/numberfield@3.8.5(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/overlays@3.8.9(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/progress@3.5.6(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/radio@3.8.3(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/searchfield@3.5.8(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/textfield': 3.9.6(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/select@3.9.6(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared@3.25.0(react@18.3.1)':
Dashboard improvements (from 24 September 2024 + 30 September 2024) (#11219) - Close https://github.com/enso-org/cloud-v2/issues/1508 - :warning: Labels modal - add selection indicator where user can (de)select multiple labels - Checkboxes currently still cause the dialog to (incorrectly) close - Edit datalink -> select enso secret -> options are too narrow for enso path. Strip enso://Users(Teams), if possible make the options list longer on the left side - Added (or rather, re-enabled via CSS) horizontal scroll instead - Make Versions, Sessions, Settings as tabs similar to documentation panel in graph editor - Edit description in context menu should open asset panel with description input active - Edit secret should be moved to asset panel (same like datalink) - Dim background when "edit description", "edit secret", or "edit datalink" are clicked/triggered via shortcut to highlight input - Hide unused (= no backend support) columns and icons: accessed by projects and accessed data - *Partial* frontend fixes for https://github.com/enso-org/cloud-v2/issues/1529 - (1) Fix settings title being horizontally centered and split on multiple lines - (2) :x: backend issue - (3) :x: out of scope - (4) :x: backend issue - (5) :x: out of scope - (6) :x: out of scope - (7) :x: backend issue - (8) :x: already fixed in #11126 - (9) :x: out of scope (potentially requires a way to trigger a tooltip on a disabled button) - (10) :x: out of scope - (11) :x: out of scope - (12) :x: out of scope - (13) URL encode `enso://` URLs in "copy as path" - (14) Double click on datalink make asset open and close (not sure if this has already been fixed) - (15) Clicking anywhere on Asset Panel no longer deselects assets (not sure if this has already been fixed) - (16) :x: addressed in #11268 - (17) Make list of labels in Asset Panel (right sidebar) horizontal instead of (incorrectly) vertical - (18) Only show "Billing" settings tab for organization admins - Use "workspace" instead of "network" icon for project tabs - Other fixes: - Fix Asset Panel (right sidebar) not being able to be toggled off if it is temporarily open (when triggered from editing description, or editing secret, or editing datalink) - Make "cancel" and "reset" buttons default to outline variant, instead of ghost variant - Fix style of dropdown - Change Datalink editor dialog so that object keys are above inputs, not beside them. This gives inputs much more horizontal space for children of deeply nested objects. Issues left to fix: - Checkboxes currently still cause the dialog to (incorrectly) close - "Edit description" actions etc. do not properly focus inputs Issues left to do (out of scope): - Show username of user currently using a project (possibly as tooltip?) if the project is currently disabled. - Dropdown and autocomplete entries should be in their own dialog, so that they can escape the parent dialog if they are too long # Important Notes None
2024-10-09 12:10:49 +03:00
dependencies:
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/slider@3.7.5(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/switch@3.5.5(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/table@3.10.1(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/grid': 3.2.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/tabs@3.3.9(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/textfield@3.9.6(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/tooltip@3.4.11(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-types/overlays': 3.8.9(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@remix-run/router@1.17.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/pluginutils@5.1.0(rollup@4.24.0)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/estree': 1.0.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
estree-walker: 2.0.2
picomatch: 2.3.1
optionalDependencies:
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
rollup: 4.24.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-android-arm-eabi@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-android-arm64@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-darwin-arm64@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-darwin-x64@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-arm-gnueabihf@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-arm-musleabihf@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-arm64-gnu@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-arm64-musl@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-powerpc64le-gnu@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-riscv64-gnu@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-s390x-gnu@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-x64-gnu@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-linux-x64-musl@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-win32-arm64-msvc@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-win32-ia32-msvc@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-win32-x64-msvc@4.24.0':
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry-internal/feedback@7.118.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/core': 7.118.0
'@sentry/types': 7.118.0
'@sentry/utils': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry-internal/replay-canvas@7.118.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/core': 7.118.0
'@sentry/replay': 7.118.0
'@sentry/types': 7.118.0
'@sentry/utils': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry-internal/tracing@7.118.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/core': 7.118.0
'@sentry/types': 7.118.0
'@sentry/utils': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/browser@7.118.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry-internal/feedback': 7.118.0
'@sentry-internal/replay-canvas': 7.118.0
'@sentry-internal/tracing': 7.118.0
'@sentry/core': 7.118.0
'@sentry/integrations': 7.118.0
'@sentry/replay': 7.118.0
'@sentry/types': 7.118.0
'@sentry/utils': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/core@7.118.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/types': 7.118.0
'@sentry/utils': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/integrations@7.118.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/core': 7.118.0
'@sentry/types': 7.118.0
'@sentry/utils': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
localforage: 1.10.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/react@7.118.0(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/browser': 7.118.0
'@sentry/core': 7.118.0
'@sentry/types': 7.118.0
'@sentry/utils': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hoist-non-react-statics: 3.3.2
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/replay@7.118.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry-internal/tracing': 7.118.0
'@sentry/core': 7.118.0
'@sentry/types': 7.118.0
'@sentry/utils': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/types@7.118.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/utils@7.118.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sentry/types': 7.118.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@shaderfrog/glsl-parser@2.1.5': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sinclair/typebox@0.27.8': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sindresorhus/is@4.6.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@smithy/is-array-buffer@2.2.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@smithy/types@3.3.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@smithy/util-buffer-from@2.2.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@smithy/is-array-buffer': 2.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@smithy/util-utf8@2.3.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@smithy/util-buffer-from': 2.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@stripe/react-stripe-js@2.7.2(@stripe/stripe-js@3.5.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@stripe/stripe-js': 3.5.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prop-types: 15.8.1
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@stripe/stripe-js@3.5.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@swc/helpers@0.5.12':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tslib: 2.6.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@szmarczak/http-timer@4.0.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
defer-to-connect: 2.0.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/match-sorter-utils@8.15.1':
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
dependencies:
remove-accents: 0.5.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/query-core@5.54.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/query-devtools@5.37.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/query-persist-client-core@5.54.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/query-core': 5.54.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/react-query-devtools@5.45.1(@tanstack/react-query@5.55.0(react@18.3.1))(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/query-devtools': 5.37.1
'@tanstack/react-query': 5.55.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/react-query@5.55.0(react@18.3.1)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/query-core': 5.54.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/vue-query@5.54.2(vue@3.5.2(typescript@5.5.3))':
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tanstack/match-sorter-utils': 8.15.1
'@tanstack/query-core': 5.54.1
'@vue/devtools-api': 6.6.3
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
vue-demi: 0.14.10(vue@3.5.2(typescript@5.5.3))
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tootallnate/once@2.0.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tsconfig/node20@20.1.4': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/babel__core@7.20.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/parser': 7.25.6
'@babel/types': 7.25.6
'@types/babel__generator': 7.6.8
'@types/babel__template': 7.4.4
'@types/babel__traverse': 7.20.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/babel__generator@7.6.8':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/babel__template@7.4.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/parser': 7.25.6
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/babel__traverse@7.20.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/cacheable-request@6.0.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/http-cache-semantics': 4.0.4
'@types/keyv': 3.1.4
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/responselike': 1.0.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/cookie@0.3.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/css.escape@1.5.2': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/culori@2.1.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-array@3.2.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-axis@3.0.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-selection': 3.0.10
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-brush@3.0.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-selection': 3.0.10
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-chord@3.0.6': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-color@3.1.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-contour@3.0.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-array': 3.2.1
'@types/geojson': 7946.0.14
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-delaunay@6.0.4': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-dispatch@3.0.6': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-drag@3.0.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-selection': 3.0.10
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-dsv@3.0.7': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-ease@3.0.2': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-fetch@3.0.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-dsv': 3.0.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-force@3.0.10': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-format@3.0.4': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-geo@3.1.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/geojson': 7946.0.14
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-hierarchy@3.1.7': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-interpolate@3.0.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-color': 3.1.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-path@3.1.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-polygon@3.0.2': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-quadtree@3.0.6': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-random@3.0.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-scale-chromatic@3.0.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-scale@4.0.8':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-time': 3.0.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-selection@3.0.10': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-shape@3.1.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-path': 3.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-time-format@4.0.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-time@3.0.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-timer@3.0.2': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-transition@3.0.8':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-selection': 3.0.10
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-zoom@3.0.8':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-interpolate': 3.0.4
'@types/d3-selection': 3.0.10
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3@7.4.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/d3-array': 3.2.1
'@types/d3-axis': 3.0.6
'@types/d3-brush': 3.0.6
'@types/d3-chord': 3.0.6
'@types/d3-color': 3.1.3
'@types/d3-contour': 3.0.6
'@types/d3-delaunay': 6.0.4
'@types/d3-dispatch': 3.0.6
'@types/d3-drag': 3.0.7
'@types/d3-dsv': 3.0.7
'@types/d3-ease': 3.0.2
'@types/d3-fetch': 3.0.7
'@types/d3-force': 3.0.10
'@types/d3-format': 3.0.4
'@types/d3-geo': 3.1.0
'@types/d3-hierarchy': 3.1.7
'@types/d3-interpolate': 3.0.4
'@types/d3-path': 3.1.0
'@types/d3-polygon': 3.0.2
'@types/d3-quadtree': 3.0.6
'@types/d3-random': 3.0.3
'@types/d3-scale': 4.0.8
'@types/d3-scale-chromatic': 3.0.3
'@types/d3-selection': 3.0.10
'@types/d3-shape': 3.1.6
'@types/d3-time': 3.0.3
'@types/d3-time-format': 4.0.3
'@types/d3-timer': 3.0.2
'@types/d3-transition': 3.0.8
'@types/d3-zoom': 3.0.8
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/debug@4.1.12':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/ms': 0.7.34
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/eslint@8.56.10':
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/estree': 1.0.6
'@types/json-schema': 7.0.15
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
optional: true
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/estree@1.0.6': {}
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/flexsearch@0.7.6': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/fs-extra@9.0.13':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/geojson@7946.0.14': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/hammerjs@2.0.45': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/hash-sum@1.0.2': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/http-cache-semantics@4.0.4': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/jsdom@21.1.7':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/tough-cookie': 4.0.5
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse5: 7.1.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/json-schema@7.0.15': {}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/keyv@3.1.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/linkify-it@5.0.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/mapbox-gl@2.7.21':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/geojson': 7946.0.14
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/markdown-it@12.2.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/linkify-it': 5.0.0
'@types/mdurl': 2.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/mdurl@2.0.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/mime-types@2.1.4': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/ms@0.7.34': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node-fetch@2.6.4':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
form-data: 3.0.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/node@20.11.21':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
undici-types: 5.26.5
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node@22.9.0':
dependencies:
undici-types: 6.19.8
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/opener@1.4.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/plist@3.0.5':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xmlbuilder: 15.1.1
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/prop-types@15.7.12': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react-dom@18.0.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react': 18.3.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react-dom@18.3.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react': 18.3.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react@18.3.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/prop-types': 15.7.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
csstype: 3.1.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/responselike@1.0.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/scheduler@0.23.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/semver@7.5.8': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/sharp@0.31.1':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/shuffle-seed@1.1.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/tar@6.1.13':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minipass: 4.2.8
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/to-ico@1.1.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/tough-cookie@4.0.5': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/validator@13.12.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/verror@1.10.10':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/web-bluetooth@0.0.20': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/wicg-file-system-access@2023.10.5': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/ws@8.5.10':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/yargs-parser@21.0.3': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/yargs@17.0.32':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/yargs-parser': 21.0.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/yauzl@2.10.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optional: true
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/eslint-plugin@8.11.0(@typescript-eslint/parser@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3))(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint-community/regexpp': 4.11.0
'@typescript-eslint/parser': 8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
'@typescript-eslint/scope-manager': 8.11.0
'@typescript-eslint/type-utils': 8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
'@typescript-eslint/utils': 8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
'@typescript-eslint/visitor-keys': 8.11.0
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
graphemer: 1.4.0
ignore: 5.3.1
natural-compare: 1.4.0
ts-api-utils: 1.3.0(typescript@5.5.3)
optionalDependencies:
typescript: 5.5.3
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/parser@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/scope-manager': 8.11.0
'@typescript-eslint/types': 8.11.0
'@typescript-eslint/typescript-estree': 8.11.0(typescript@5.5.3)
'@typescript-eslint/visitor-keys': 8.11.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optionalDependencies:
typescript: 5.5.3
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/scope-manager@8.11.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/types': 8.11.0
'@typescript-eslint/visitor-keys': 8.11.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/type-utils@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/typescript-estree': 8.11.0(typescript@5.5.3)
'@typescript-eslint/utils': 8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ts-api-utils: 1.3.0(typescript@5.5.3)
optionalDependencies:
typescript: 5.5.3
transitivePeerDependencies:
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
- eslint
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/types@8.11.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/typescript-estree@8.11.0(typescript@5.5.3)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/types': 8.11.0
'@typescript-eslint/visitor-keys': 8.11.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
fast-glob: 3.3.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
is-glob: 4.0.3
minimatch: 9.0.5
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ts-api-utils: 1.3.0(typescript@5.5.3)
optionalDependencies:
typescript: 5.5.3
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/utils@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint-community/eslint-utils': 4.4.0(eslint@9.13.0(jiti@1.21.6))
'@typescript-eslint/scope-manager': 8.11.0
'@typescript-eslint/types': 8.11.0
'@typescript-eslint/typescript-estree': 8.11.0(typescript@5.5.3)
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
- typescript
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/visitor-keys@8.11.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/types': 8.11.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
eslint-visitor-keys: 3.4.3
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@vitejs/plugin-react@4.3.3(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/plugin-transform-react-jsx-self': 7.24.7(@babel/core@7.25.2)
'@babel/plugin-transform-react-jsx-source': 7.24.7(@babel/core@7.25.2)
'@types/babel__core': 7.20.5
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-refresh: 0.14.2
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@vitejs/plugin-vue@5.0.5(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))(vue@3.5.2(typescript@5.5.3))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@vitest/coverage-v8@1.6.0(vitest@1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ampproject/remapping': 2.3.0
'@bcoe/v8-coverage': 0.2.3
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
istanbul-lib-coverage: 3.2.2
istanbul-lib-report: 3.0.1
istanbul-lib-source-maps: 5.0.5
istanbul-reports: 3.1.7
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
magic-string: 0.30.11
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
magicast: 0.3.4
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
std-env: 3.7.0
strip-literal: 2.1.0
test-exclude: 6.0.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vitest: 1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/expect@1.6.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/spy': 1.6.0
'@vitest/utils': 1.6.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chai: 4.4.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/runner@1.6.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/utils': 1.6.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
p-limit: 5.0.0
pathe: 1.1.2
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/snapshot@1.6.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
magic-string: 0.30.11
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pathe: 1.1.2
pretty-format: 29.7.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/spy@1.6.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
tinyspy: 2.2.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/utils@1.6.0':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
diff-sequences: 29.6.3
estree-walker: 3.0.3
loupe: 2.3.7
pretty-format: 29.7.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@volar/language-core@2.4.0-alpha.12':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@volar/source-map': 2.4.0-alpha.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@volar/source-map@2.4.0-alpha.12': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@volar/typescript@2.4.0-alpha.12':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@volar/language-core': 2.4.0-alpha.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-browserify: 1.0.1
vscode-uri: 3.0.8
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/babel-helper-vue-transform-on@1.2.2': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/babel-plugin-jsx@1.2.2(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/helper-module-imports': 7.22.15
'@babel/helper-plugin-utils': 7.24.7
'@babel/plugin-syntax-jsx': 7.24.7(@babel/core@7.25.2)
'@babel/template': 7.25.0
'@babel/traverse': 7.25.6
'@babel/types': 7.25.6
'@vue/babel-helper-vue-transform-on': 1.2.2
'@vue/babel-plugin-resolve-type': 1.2.2(@babel/core@7.25.2)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
camelcase: 6.3.0
html-tags: 3.3.1
svg-tags: 1.0.0
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/babel-plugin-resolve-type@1.2.2(@babel/core@7.25.2)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/code-frame': 7.24.7
'@babel/core': 7.25.2
'@babel/helper-module-imports': 7.22.15
'@babel/helper-plugin-utils': 7.24.7
'@babel/parser': 7.25.6
'@vue/compiler-sfc': 3.5.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-core@3.5.2':
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/parser': 7.25.6
'@vue/shared': 3.5.2
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
entities: 4.5.0
estree-walker: 2.0.2
source-map-js: 1.2.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-dom@3.5.2':
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-core': 3.5.2
'@vue/shared': 3.5.2
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-sfc@3.5.2':
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/parser': 7.25.6
'@vue/compiler-core': 3.5.2
'@vue/compiler-dom': 3.5.2
'@vue/compiler-ssr': 3.5.2
'@vue/shared': 3.5.2
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
estree-walker: 2.0.2
magic-string: 0.30.11
postcss: 8.4.45
source-map-js: 1.2.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-ssr@3.5.2':
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-dom': 3.5.2
'@vue/shared': 3.5.2
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/devtools-api@6.6.3': {}
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-core@7.6.3(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))(vue@3.5.2(typescript@5.5.3))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-kit': 7.6.3
'@vue/devtools-shared': 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mitt: 3.0.1
nanoid: 3.3.7
pathe: 1.1.2
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite-hot-client: 0.2.3(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- vite
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-kit@7.6.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-shared': 7.6.3
birpc: 0.2.19
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
hookable: 5.5.3
mitt: 3.0.1
perfect-debounce: 1.0.0
speakingurl: 14.0.1
superjson: 2.2.1
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-shared@7.6.3':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
rfdc: 1.4.1
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/eslint-config-typescript@14.1.3(@typescript-eslint/parser@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3))(eslint-plugin-vue@9.29.1(eslint@9.13.0(jiti@1.21.6)))(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/eslint-plugin': 8.11.0(@typescript-eslint/parser@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3))(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
eslint-plugin-vue: 9.29.1(eslint@9.13.0(jiti@1.21.6))
fast-glob: 3.3.2
Metadata should not depend on absolute text spans (#11390) close #11304 Changelog: - update: add `ide.snapshot` optional metadata field containing the source code of the file - update: `syncFileContents` method tries to repair the metadata spans when it detects that the source file was edited and the received code does not match the code stored in the `ide.snapshot` metadata field # Important Notes Tested in gui
2024-10-28 12:41:46 +03:00
typescript-eslint: 8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
vue-eslint-parser: 9.4.3(eslint@9.13.0(jiti@1.21.6))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optionalDependencies:
typescript: 5.5.3
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@typescript-eslint/parser'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- supports-color
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/language-core@2.0.24(typescript@5.5.3)':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@volar/language-core': 2.4.0-alpha.12
'@vue/compiler-dom': 3.5.2
'@vue/shared': 3.5.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
computeds: 0.0.1
minimatch: 9.0.5
muggle-string: 0.4.1
path-browserify: 1.0.1
vue-template-compiler: 2.7.16
optionalDependencies:
typescript: 5.5.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/reactivity@3.5.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/shared': 3.5.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/runtime-core@3.5.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/reactivity': 3.5.2
'@vue/shared': 3.5.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/runtime-dom@3.5.2':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/reactivity': 3.5.2
'@vue/runtime-core': 3.5.2
'@vue/shared': 3.5.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
csstype: 3.1.3
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/server-renderer@3.5.2(vue@3.5.2(typescript@5.5.3))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-ssr': 3.5.2
'@vue/shared': 3.5.2
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/shared@3.5.2': {}
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/test-utils@2.4.6':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
js-beautify: 1.15.1
Table Editor Widget (#10774) Fixes #10293 The Table Editor Widget allows adding rows and columns, editing cells and renaming columns. [Screencast from 2024-08-07 13-17-37.webm](https://github.com/user-attachments/assets/d2e708b5-6516-4107-bc17-f018e455c111) # Important Notes * The parts of Table Visualization which were useful for the widget were put in vue component. On this occasion, we use aggrid vue.
2024-08-12 17:45:58 +03:00
vue-component-type-helpers: 2.0.29
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/tsconfig@0.5.1': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vueuse/core@10.11.0(vue@3.5.2(typescript@5.5.3))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/web-bluetooth': 0.0.20
'@vueuse/metadata': 10.11.0
'@vueuse/shared': 10.11.0(vue@3.5.2(typescript@5.5.3))
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
vue-demi: 0.14.10(vue@3.5.2(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@vue/composition-api'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- vue
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vueuse/gesture@2.0.0(vue@3.5.2(typescript@5.5.3))':
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
dependencies:
chokidar: 3.6.0
consola: 3.2.3
upath: 2.0.1
vue: 3.5.2(typescript@5.5.3)
vue-demi: 0.14.10(vue@3.5.2(typescript@5.5.3))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vueuse/metadata@10.11.0': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vueuse/shared@10.11.0(vue@3.5.2(typescript@5.5.3))':
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue-demi: 0.14.10(vue@3.5.2(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@vue/composition-api'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- vue
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@xmldom/xmldom@0.8.10': {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
abbrev@2.0.0: {}
abstract-leveldown@6.2.3:
dependencies:
buffer: 5.7.1
immediate: 3.3.0
level-concat-iterator: 2.0.1
level-supports: 1.0.1
xtend: 4.0.2
optional: true
abstract-leveldown@6.3.0:
dependencies:
buffer: 5.7.1
immediate: 3.3.0
level-concat-iterator: 2.0.1
level-supports: 1.0.1
xtend: 4.0.2
optional: true
acorn-jsx@5.3.2(acorn@8.12.0):
dependencies:
acorn: 8.12.0
acorn-walk@8.3.3:
dependencies:
acorn: 8.12.0
acorn@8.12.0: {}
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-charts-community@9.3.2: {}
ag-grid-community@31.3.4: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-grid-enterprise@31.3.4:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-charts-community: 9.3.2
ag-grid-community: 31.3.4
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-grid-vue3@31.3.4(typescript@5.5.3):
Table Editor Widget (#10774) Fixes #10293 The Table Editor Widget allows adding rows and columns, editing cells and renaming columns. [Screencast from 2024-08-07 13-17-37.webm](https://github.com/user-attachments/assets/d2e708b5-6516-4107-bc17-f018e455c111) # Important Notes * The parts of Table Visualization which were useful for the widget were put in vue component. On this occasion, we use aggrid vue.
2024-08-12 17:45:58 +03:00
dependencies:
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
ag-grid-community: 31.3.4
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
Table Widget: removing columns and rows (#11151) Fixes: #10758 [Screencast from 2024-09-23 13-19-31.webm](https://github.com/user-attachments/assets/aa28708e-f4c9-400a-966d-1d82abe99f1e) # Important Notes To add custom options, I needed to bump AGGrid version. But not the newest one, as it made some bugs I failed to fix.
2024-09-23 17:24:40 +03:00
transitivePeerDependencies:
- typescript
Table Editor Widget (#10774) Fixes #10293 The Table Editor Widget allows adding rows and columns, editing cells and renaming columns. [Screencast from 2024-08-07 13-17-37.webm](https://github.com/user-attachments/assets/d2e708b5-6516-4107-bc17-f018e455c111) # Important Notes * The parts of Table Visualization which were useful for the widget were put in vue component. On this occasion, we use aggrid vue.
2024-08-12 17:45:58 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
agent-base@6.0.2:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
agent-base@7.1.1:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
ajv-keywords@3.5.2(ajv@6.12.6):
dependencies:
ajv: 6.12.6
ajv@6.12.6:
dependencies:
fast-deep-equal: 3.1.3
fast-json-stable-stringify: 2.1.0
json-schema-traverse: 0.4.1
uri-js: 4.4.1
ajv@8.16.0:
dependencies:
fast-deep-equal: 3.1.3
json-schema-traverse: 1.0.0
require-from-string: 2.0.2
uri-js: 4.4.1
amazon-cognito-identity-js@6.3.6:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@aws-crypto/sha256-js': 1.2.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer: 4.9.2
fast-base64-decode: 1.0.0
isomorphic-unfetch: 3.1.0
js-cookie: 2.2.1
transitivePeerDependencies:
- encoding
ansi-regex@5.0.1: {}
ansi-regex@6.0.1: {}
ansi-styles@3.2.1:
dependencies:
color-convert: 1.9.3
ansi-styles@4.3.0:
dependencies:
color-convert: 2.0.1
ansi-styles@5.2.0: {}
ansi-styles@6.2.1: {}
any-promise@1.3.0: {}
anymatch@3.1.3:
dependencies:
normalize-path: 3.0.0
picomatch: 2.3.1
app-builder-bin@4.0.0: {}
Optimize asset table rendering (#11382) - Depends on: - #11380 - Some optimizations for re-rendering assets table: - Omit `visibilities` from `state` in favor of passing each `AssetRow`'s `visibility` directly to the row. This minimizes spurious `state` updates. - Pass `id` and `parentId` to `AssetRow` instead of the entire object. This ensures that re-fetches do not force a re-render of the `AssetRow` - we are no longer passing a reference to the object, so we are now comparing by string comparison (which is almost always stable). # Important Notes None
2024-10-31 13:36:10 +03:00
app-builder-lib@24.13.3(dmg-builder@24.13.3(electron-builder-squirrel-windows@24.13.3))(electron-builder-squirrel-windows@24.13.3(dmg-builder@24.13.3)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@develar/schema-utils': 2.6.5
'@electron/notarize': 2.2.1
'@electron/osx-sign': 1.0.5
'@electron/universal': 1.5.1
'@malept/flatpak-bundler': 0.4.0
'@types/fs-extra': 9.0.13
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
async-exit-hook: 2.0.1
bluebird-lst: 1.0.9
builder-util: 24.13.1
builder-util-runtime: 9.2.4
chromium-pickle-js: 0.2.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dmg-builder: 24.13.3(electron-builder-squirrel-windows@24.13.3)
ejs: 3.1.10
electron-builder-squirrel-windows: 24.13.3(dmg-builder@24.13.3)
electron-publish: 24.13.1
form-data: 4.0.0
fs-extra: 10.1.0
hosted-git-info: 4.1.0
is-ci: 3.0.1
isbinaryfile: 5.0.2
js-yaml: 4.1.0
lazy-val: 1.0.5
minimatch: 5.1.6
read-config-file: 6.3.2
sanitize-filename: 1.6.3
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tar: 6.2.1
temp-file: 3.4.0
transitivePeerDependencies:
- supports-color
archiver-utils@2.1.0:
dependencies:
glob: 7.2.3
graceful-fs: 4.2.11
lazystream: 1.0.1
lodash.defaults: 4.2.0
lodash.difference: 4.5.0
lodash.flatten: 4.4.0
lodash.isplainobject: 4.0.6
lodash.union: 4.6.0
normalize-path: 3.0.0
readable-stream: 2.3.8
archiver-utils@3.0.4:
dependencies:
glob: 7.2.3
graceful-fs: 4.2.11
lazystream: 1.0.1
lodash.defaults: 4.2.0
lodash.difference: 4.5.0
lodash.flatten: 4.4.0
lodash.isplainobject: 4.0.6
lodash.union: 4.6.0
normalize-path: 3.0.0
readable-stream: 3.6.2
archiver@5.3.2:
dependencies:
archiver-utils: 2.1.0
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
async: 3.2.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-crc32: 0.2.13
readable-stream: 3.6.2
readdir-glob: 1.1.3
tar-stream: 2.2.0
zip-stream: 4.1.1
are-docs-informative@0.0.2: {}
arg@5.0.2: {}
argparse@1.0.10:
dependencies:
sprintf-js: 1.0.3
argparse@2.0.1: {}
array-buffer-byte-length@1.0.1:
dependencies:
call-bind: 1.0.7
is-array-buffer: 3.0.4
array-includes@3.1.8:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-object-atoms: 1.0.0
get-intrinsic: 1.2.4
is-string: 1.0.7
array.prototype.findlast@1.2.5:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-errors: 1.3.0
es-object-atoms: 1.0.0
es-shim-unscopables: 1.0.2
array.prototype.flat@1.3.2:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-shim-unscopables: 1.0.2
array.prototype.flatmap@1.3.2:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-shim-unscopables: 1.0.2
array.prototype.tosorted@1.1.4:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-errors: 1.3.0
es-shim-unscopables: 1.0.2
arraybuffer.prototype.slice@1.0.3:
dependencies:
array-buffer-byte-length: 1.0.1
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-errors: 1.3.0
get-intrinsic: 1.2.4
is-array-buffer: 3.0.4
is-shared-array-buffer: 1.0.3
arrify@1.0.1: {}
asn1@0.2.6:
dependencies:
safer-buffer: 2.1.2
assert-plus@1.0.0: {}
assertion-error@1.1.0: {}
astral-regex@2.0.0:
optional: true
async-exit-hook@2.0.1: {}
async@2.6.4:
dependencies:
lodash: 4.17.21
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
async@3.2.6: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
asynckit@0.4.0: {}
at-least-node@1.0.0: {}
available-typed-arrays@1.0.7:
dependencies:
possible-typed-array-names: 1.0.0
aws-sign2@0.7.0: {}
aws4@1.13.0: {}
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
babel-plugin-react-compiler@19.0.0-beta-6fc168f-20241025:
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/types': 7.25.6
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
balanced-match@1.0.2: {}
base64-js@1.5.1: {}
bcrypt-pbkdf@1.0.2:
dependencies:
tweetnacl: 0.14.5
bignumber.js@2.4.0: {}
binary-extensions@2.3.0: {}
birpc@0.1.1: {}
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
birpc@0.2.19: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
bl@4.1.0:
dependencies:
buffer: 5.7.1
inherits: 2.0.4
readable-stream: 3.6.2
bluebird-lst@1.0.9:
dependencies:
bluebird: 3.7.2
bluebird@3.7.2: {}
bmp-js@0.0.1: {}
bmp-js@0.0.3: {}
body-parser@1.20.2:
dependencies:
bytes: 3.1.2
content-type: 1.0.5
debug: 2.6.9
depd: 2.0.0
destroy: 1.2.0
http-errors: 2.0.0
iconv-lite: 0.4.24
on-finished: 2.4.1
qs: 6.11.0
raw-body: 2.5.2
type-is: 1.6.18
unpipe: 1.0.0
transitivePeerDependencies:
- supports-color
boolbase@1.0.0: {}
boolean@3.2.0:
optional: true
bowser@2.11.0: {}
brace-expansion@1.1.11:
dependencies:
balanced-match: 1.0.2
concat-map: 0.0.1
brace-expansion@2.0.1:
dependencies:
balanced-match: 1.0.2
braces@3.0.2:
dependencies:
fill-range: 7.0.1
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
browserslist@4.23.3:
dependencies:
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
caniuse-lite: 1.0.30001658
electron-to-chromium: 1.5.16
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
node-releases: 2.0.18
update-browserslist-db: 1.1.0(browserslist@4.23.3)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
buffer-alloc-unsafe@1.1.0: {}
buffer-alloc@1.2.0:
dependencies:
buffer-alloc-unsafe: 1.1.0
buffer-fill: 1.0.0
buffer-crc32@0.2.13: {}
buffer-equal@0.0.1: {}
buffer-equal@1.0.1: {}
buffer-fill@1.0.0: {}
buffer-from@1.1.2: {}
buffer@4.9.2:
dependencies:
base64-js: 1.5.1
ieee754: 1.2.1
isarray: 1.0.0
buffer@5.7.1:
dependencies:
base64-js: 1.5.1
ieee754: 1.2.1
builder-util-runtime@9.2.4:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sax: 1.4.1
transitivePeerDependencies:
- supports-color
builder-util@24.13.1:
dependencies:
7zip-bin: 5.2.0
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/debug': 4.1.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
app-builder-bin: 4.0.0
bluebird-lst: 1.0.9
builder-util-runtime: 9.2.4
chalk: 4.1.2
cross-spawn: 7.0.3
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra: 10.1.0
http-proxy-agent: 5.0.0
https-proxy-agent: 5.0.1
is-ci: 3.0.1
js-yaml: 4.1.0
source-map-support: 0.5.21
stat-mode: 1.0.0
temp-file: 3.4.0
transitivePeerDependencies:
- supports-color
bundle-name@4.1.0:
dependencies:
run-applescript: 7.0.0
bytes@3.1.2: {}
cac@6.7.14: {}
cacheable-lookup@5.0.4: {}
cacheable-request@7.0.4:
dependencies:
clone-response: 1.0.3
get-stream: 5.2.0
http-cache-semantics: 4.1.1
keyv: 4.5.4
lowercase-keys: 2.0.0
normalize-url: 6.1.0
responselike: 2.0.1
call-bind@1.0.7:
dependencies:
es-define-property: 1.0.0
es-errors: 1.3.0
function-bind: 1.1.2
get-intrinsic: 1.2.4
set-function-length: 1.2.1
call-me-maybe@1.0.2: {}
callsites@3.1.0: {}
camel-case@4.1.2:
dependencies:
pascal-case: 3.1.2
tslib: 2.6.3
camelcase-css@2.0.1: {}
camelcase@6.3.0: {}
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
caniuse-lite@1.0.30001658: {}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
capital-case@1.0.4:
dependencies:
no-case: 3.0.4
tslib: 2.6.3
upper-case-first: 2.0.2
caseless@0.12.0: {}
chai@4.4.1:
dependencies:
assertion-error: 1.1.0
check-error: 1.0.3
deep-eql: 4.1.4
get-func-name: 2.0.2
loupe: 2.3.7
pathval: 1.1.1
type-detect: 4.0.8
chalk@2.4.2:
dependencies:
ansi-styles: 3.2.1
escape-string-regexp: 1.0.5
supports-color: 5.5.0
chalk@4.1.2:
dependencies:
ansi-styles: 4.3.0
supports-color: 7.2.0
chalk@5.3.0: {}
change-case@4.1.2:
dependencies:
camel-case: 4.1.2
capital-case: 1.0.4
constant-case: 3.0.4
dot-case: 3.0.4
header-case: 2.0.4
no-case: 3.0.4
param-case: 3.0.4
pascal-case: 3.1.2
path-case: 3.0.4
sentence-case: 3.0.4
snake-case: 3.0.4
tslib: 2.6.3
char-regex@2.0.1: {}
check-error@1.0.3:
dependencies:
get-func-name: 2.0.2
chokidar@3.6.0:
dependencies:
anymatch: 3.1.3
braces: 3.0.2
glob-parent: 5.1.2
is-binary-path: 2.1.0
is-glob: 4.0.3
normalize-path: 3.0.0
readdirp: 3.6.0
optionalDependencies:
fsevents: 2.3.3
chownr@1.1.4: {}
chownr@2.0.0: {}
chromium-pickle-js@0.2.0: {}
ci-info@3.9.0: {}
cli-truncate@2.1.0:
dependencies:
slice-ansi: 3.0.0
string-width: 4.2.3
optional: true
client-only@0.0.1: {}
cliui@8.0.1:
dependencies:
string-width: 4.2.3
strip-ansi: 6.0.1
wrap-ansi: 7.0.0
clone-response@1.0.3:
dependencies:
mimic-response: 1.0.1
clsx@1.2.1: {}
clsx@2.1.1: {}
codemirror@6.0.1(@lezer/common@1.2.1):
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@codemirror/autocomplete': 6.16.3(@codemirror/language@6.10.2)(@codemirror/state@6.4.1)(@codemirror/view@6.28.3)(@lezer/common@1.2.1)
'@codemirror/commands': 6.6.0
'@codemirror/language': 6.10.2
'@codemirror/lint': 6.8.1
'@codemirror/search': 6.5.6
'@codemirror/state': 6.4.1
'@codemirror/view': 6.28.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@lezer/common'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
color-convert@1.9.3:
dependencies:
color-name: 1.1.3
color-convert@2.0.1:
dependencies:
color-name: 1.1.4
color-name@1.1.3: {}
color-name@1.1.4: {}
color-string@1.9.1:
dependencies:
color-name: 1.1.4
simple-swizzle: 0.2.2
color@4.2.3:
dependencies:
color-convert: 2.0.1
color-string: 1.9.1
combined-stream@1.0.8:
dependencies:
delayed-stream: 1.0.0
commander@10.0.1: {}
commander@11.1.0: {}
commander@2.20.3: {}
commander@4.1.1: {}
commander@5.1.0: {}
commander@7.2.0: {}
comment-parser@1.4.1: {}
compare-version@0.1.2: {}
compress-commons@4.1.2:
dependencies:
buffer-crc32: 0.2.13
crc32-stream: 4.0.3
normalize-path: 3.0.0
readable-stream: 3.6.2
computeds@0.0.1: {}
concat-map@0.0.1: {}
confbox@0.1.7: {}
config-chain@1.1.13:
dependencies:
ini: 1.3.8
proto-list: 1.2.4
config-file-ts@0.2.6:
dependencies:
glob: 10.4.2
typescript: 5.5.3
connect@3.7.0:
dependencies:
debug: 2.6.9
finalhandler: 1.1.2
parseurl: 1.3.3
utils-merge: 1.0.1
transitivePeerDependencies:
- supports-color
connected@0.0.2: {}
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
consola@3.2.3: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
constant-case@3.0.4:
dependencies:
no-case: 3.0.4
tslib: 2.6.3
upper-case: 2.0.2
content-type@1.0.5: {}
convert-source-map@2.0.0: {}
cookie@0.4.2: {}
copy-anything@3.0.5:
dependencies:
is-what: 4.1.16
core-util-is@1.0.2: {}
core-util-is@1.0.3: {}
cors@2.8.5:
dependencies:
object-assign: 4.1.1
vary: 1.1.2
crc-32@1.2.2: {}
crc32-stream@4.0.3:
dependencies:
crc-32: 1.2.2
readable-stream: 3.6.2
crc@3.8.0:
dependencies:
buffer: 5.7.1
optional: true
create-servers@3.2.0:
dependencies:
connected: 0.0.2
errs: 0.3.2
object-assign: 4.1.1
crelt@1.0.6: {}
cross-env@7.0.3:
dependencies:
cross-spawn: 7.0.3
cross-spawn@6.0.5:
dependencies:
nice-try: 1.0.5
path-key: 2.0.1
semver: 5.7.2
shebang-command: 1.2.0
which: 1.3.1
cross-spawn@7.0.3:
dependencies:
path-key: 3.1.1
shebang-command: 2.0.0
which: 2.0.2
css-select@5.1.0:
dependencies:
boolbase: 1.0.0
css-what: 6.1.0
domhandler: 5.0.3
domutils: 3.1.0
nth-check: 2.1.1
css-what@6.1.0: {}
css.escape@1.5.1: {}
cssesc@3.0.0: {}
cssstyle@4.0.1:
dependencies:
rrweb-cssom: 0.6.0
csstype@3.1.3: {}
culori@3.3.0: {}
d3-array@3.2.4:
dependencies:
internmap: 2.0.3
d3-axis@3.0.0: {}
d3-brush@3.0.0:
dependencies:
d3-dispatch: 3.0.1
d3-drag: 3.0.0
d3-interpolate: 3.0.1
d3-selection: 3.0.0
d3-transition: 3.0.1(d3-selection@3.0.0)
d3-chord@3.0.1:
dependencies:
d3-path: 3.1.0
d3-color@3.1.0: {}
d3-contour@4.0.2:
dependencies:
d3-array: 3.2.4
d3-delaunay@6.0.4:
dependencies:
delaunator: 5.0.1
d3-dispatch@3.0.1: {}
d3-drag@3.0.0:
dependencies:
d3-dispatch: 3.0.1
d3-selection: 3.0.0
d3-dsv@3.0.1:
dependencies:
commander: 7.2.0
iconv-lite: 0.6.3
rw: 1.3.3
d3-ease@3.0.1: {}
d3-fetch@3.0.1:
dependencies:
d3-dsv: 3.0.1
d3-force@3.0.0:
dependencies:
d3-dispatch: 3.0.1
d3-quadtree: 3.0.1
d3-timer: 3.0.1
d3-format@3.1.0: {}
d3-geo@3.1.1:
dependencies:
d3-array: 3.2.4
d3-hierarchy@3.1.2: {}
d3-interpolate@3.0.1:
dependencies:
d3-color: 3.1.0
d3-path@3.1.0: {}
d3-polygon@3.0.1: {}
d3-quadtree@3.0.1: {}
d3-random@3.0.1: {}
d3-scale-chromatic@3.1.0:
dependencies:
d3-color: 3.1.0
d3-interpolate: 3.0.1
d3-scale@4.0.2:
dependencies:
d3-array: 3.2.4
d3-format: 3.1.0
d3-interpolate: 3.0.1
d3-time: 3.1.0
d3-time-format: 4.1.0
d3-selection@3.0.0: {}
d3-shape@3.2.0:
dependencies:
d3-path: 3.1.0
d3-time-format@4.1.0:
dependencies:
d3-time: 3.1.0
d3-time@3.1.0:
dependencies:
d3-array: 3.2.4
d3-timer@3.0.1: {}
d3-transition@3.0.1(d3-selection@3.0.0):
dependencies:
d3-color: 3.1.0
d3-dispatch: 3.0.1
d3-ease: 3.0.1
d3-interpolate: 3.0.1
d3-selection: 3.0.0
d3-timer: 3.0.1
d3-zoom@3.0.0:
dependencies:
d3-dispatch: 3.0.1
d3-drag: 3.0.0
d3-interpolate: 3.0.1
d3-selection: 3.0.0
d3-transition: 3.0.1(d3-selection@3.0.0)
d3@7.9.0:
dependencies:
d3-array: 3.2.4
d3-axis: 3.0.0
d3-brush: 3.0.0
d3-chord: 3.0.1
d3-color: 3.1.0
d3-contour: 4.0.2
d3-delaunay: 6.0.4
d3-dispatch: 3.0.1
d3-drag: 3.0.0
d3-dsv: 3.0.1
d3-ease: 3.0.1
d3-fetch: 3.0.1
d3-force: 3.0.0
d3-format: 3.1.0
d3-geo: 3.1.1
d3-hierarchy: 3.1.2
d3-interpolate: 3.0.1
d3-path: 3.1.0
d3-polygon: 3.0.1
d3-quadtree: 3.0.1
d3-random: 3.0.1
d3-scale: 4.0.2
d3-scale-chromatic: 3.1.0
d3-selection: 3.0.0
d3-shape: 3.2.0
d3-time: 3.1.0
d3-time-format: 4.1.0
d3-timer: 3.0.1
d3-transition: 3.0.1(d3-selection@3.0.0)
d3-zoom: 3.0.0
dashdash@1.14.1:
dependencies:
assert-plus: 1.0.0
data-urls@5.0.0:
dependencies:
whatwg-mimetype: 4.0.0
whatwg-url: 14.0.0
data-view-buffer@1.0.1:
dependencies:
call-bind: 1.0.7
es-errors: 1.3.0
is-data-view: 1.0.1
data-view-byte-length@1.0.1:
dependencies:
call-bind: 1.0.7
es-errors: 1.3.0
is-data-view: 1.0.1
data-view-byte-offset@1.0.0:
dependencies:
call-bind: 1.0.7
es-errors: 1.3.0
is-data-view: 1.0.1
de-indent@1.0.2: {}
debug@2.6.9:
dependencies:
ms: 2.0.0
debug@3.2.7:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
ms: 2.1.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
debug@4.3.7:
dependencies:
ms: 2.1.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
decimal.js@10.4.3: {}
decompress-response@6.0.0:
dependencies:
mimic-response: 3.1.0
deep-eql@4.1.4:
dependencies:
type-detect: 4.0.8
deep-extend@0.6.0: {}
deep-is@0.1.4: {}
default-browser-id@5.0.0: {}
default-browser@5.2.1:
dependencies:
bundle-name: 4.1.0
default-browser-id: 5.0.0
defer-to-connect@2.0.1: {}
deferred-leveldown@5.3.0:
dependencies:
abstract-leveldown: 6.2.3
inherits: 2.0.4
optional: true
define-data-property@1.1.4:
dependencies:
es-define-property: 1.0.0
es-errors: 1.3.0
gopd: 1.0.1
define-lazy-prop@3.0.0: {}
define-properties@1.2.1:
dependencies:
define-data-property: 1.1.4
has-property-descriptors: 1.0.2
object-keys: 1.1.1
defu@6.1.4: {}
delaunator@5.0.1:
dependencies:
robust-predicates: 3.0.2
delayed-stream@1.0.0: {}
depd@2.0.0: {}
destroy@1.2.0: {}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
detect-libc@1.0.3:
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
detect-libc@2.0.3: {}
detect-node@2.1.0: {}
diacritics@1.3.0: {}
didyoumean@1.2.2: {}
diff-sequences@29.6.3: {}
dir-compare@3.3.0:
dependencies:
buffer-equal: 1.0.1
minimatch: 3.1.2
dir-glob@3.0.1:
dependencies:
path-type: 4.0.0
discontinuous-range@1.0.0: {}
dlv@1.1.3: {}
dmg-builder@24.13.3(electron-builder-squirrel-windows@24.13.3):
dependencies:
Optimize asset table rendering (#11382) - Depends on: - #11380 - Some optimizations for re-rendering assets table: - Omit `visibilities` from `state` in favor of passing each `AssetRow`'s `visibility` directly to the row. This minimizes spurious `state` updates. - Pass `id` and `parentId` to `AssetRow` instead of the entire object. This ensures that re-fetches do not force a re-render of the `AssetRow` - we are no longer passing a reference to the object, so we are now comparing by string comparison (which is almost always stable). # Important Notes None
2024-10-31 13:36:10 +03:00
app-builder-lib: 24.13.3(dmg-builder@24.13.3(electron-builder-squirrel-windows@24.13.3))(electron-builder-squirrel-windows@24.13.3(dmg-builder@24.13.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
builder-util: 24.13.1
builder-util-runtime: 9.2.4
fs-extra: 10.1.0
iconv-lite: 0.6.3
js-yaml: 4.1.0
optionalDependencies:
dmg-license: 1.0.11
transitivePeerDependencies:
- electron-builder-squirrel-windows
- supports-color
dmg-license@1.0.11:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/plist': 3.0.5
'@types/verror': 1.10.10
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ajv: 6.12.6
crc: 3.8.0
iconv-corefoundation: 1.1.7
plist: 3.1.0
smart-buffer: 4.2.0
verror: 1.10.1
optional: true
doctrine@2.1.0:
dependencies:
esutils: 2.0.3
dom-serializer@2.0.0:
dependencies:
domelementtype: 2.3.0
domhandler: 5.0.3
entities: 4.5.0
dom-walk@0.1.2: {}
domelementtype@2.3.0: {}
domhandler@5.0.3:
dependencies:
domelementtype: 2.3.0
domutils@3.1.0:
dependencies:
dom-serializer: 2.0.0
domelementtype: 2.3.0
domhandler: 5.0.3
dot-case@3.0.4:
dependencies:
no-case: 3.0.4
tslib: 2.6.3
dotenv-expand@5.1.0: {}
dotenv@9.0.2: {}
eastasianwidth@0.2.0: {}
easy-stack@1.0.1: {}
ecc-jsbn@0.1.2:
dependencies:
jsbn: 0.1.1
safer-buffer: 2.1.2
editorconfig@1.0.4:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@one-ini/wasm': 0.1.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
commander: 10.0.1
minimatch: 9.0.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ee-first@1.1.1: {}
ejs@3.1.10:
dependencies:
jake: 10.9.1
electron-builder-squirrel-windows@24.13.3(dmg-builder@24.13.3):
dependencies:
Optimize asset table rendering (#11382) - Depends on: - #11380 - Some optimizations for re-rendering assets table: - Omit `visibilities` from `state` in favor of passing each `AssetRow`'s `visibility` directly to the row. This minimizes spurious `state` updates. - Pass `id` and `parentId` to `AssetRow` instead of the entire object. This ensures that re-fetches do not force a re-render of the `AssetRow` - we are no longer passing a reference to the object, so we are now comparing by string comparison (which is almost always stable). # Important Notes None
2024-10-31 13:36:10 +03:00
app-builder-lib: 24.13.3(dmg-builder@24.13.3(electron-builder-squirrel-windows@24.13.3))(electron-builder-squirrel-windows@24.13.3(dmg-builder@24.13.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
archiver: 5.3.2
builder-util: 24.13.1
fs-extra: 10.1.0
transitivePeerDependencies:
- dmg-builder
- supports-color
Optimize asset table rendering (#11382) - Depends on: - #11380 - Some optimizations for re-rendering assets table: - Omit `visibilities` from `state` in favor of passing each `AssetRow`'s `visibility` directly to the row. This minimizes spurious `state` updates. - Pass `id` and `parentId` to `AssetRow` instead of the entire object. This ensures that re-fetches do not force a re-render of the `AssetRow` - we are no longer passing a reference to the object, so we are now comparing by string comparison (which is almost always stable). # Important Notes None
2024-10-31 13:36:10 +03:00
electron-builder@24.13.3(electron-builder-squirrel-windows@24.13.3(dmg-builder@24.13.3)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Optimize asset table rendering (#11382) - Depends on: - #11380 - Some optimizations for re-rendering assets table: - Omit `visibilities` from `state` in favor of passing each `AssetRow`'s `visibility` directly to the row. This minimizes spurious `state` updates. - Pass `id` and `parentId` to `AssetRow` instead of the entire object. This ensures that re-fetches do not force a re-render of the `AssetRow` - we are no longer passing a reference to the object, so we are now comparing by string comparison (which is almost always stable). # Important Notes None
2024-10-31 13:36:10 +03:00
app-builder-lib: 24.13.3(dmg-builder@24.13.3(electron-builder-squirrel-windows@24.13.3))(electron-builder-squirrel-windows@24.13.3(dmg-builder@24.13.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
builder-util: 24.13.1
builder-util-runtime: 9.2.4
chalk: 4.1.2
dmg-builder: 24.13.3(electron-builder-squirrel-windows@24.13.3)
fs-extra: 10.1.0
is-ci: 3.0.1
lazy-val: 1.0.5
read-config-file: 6.3.2
simple-update-notifier: 2.0.0
yargs: 17.6.2
transitivePeerDependencies:
- electron-builder-squirrel-windows
- supports-color
electron-is-dev@2.0.0: {}
electron-publish@24.13.1:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/fs-extra': 9.0.13
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
builder-util: 24.13.1
builder-util-runtime: 9.2.4
chalk: 4.1.2
fs-extra: 10.1.0
lazy-val: 1.0.5
mime: 2.6.0
transitivePeerDependencies:
- supports-color
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
electron-to-chromium@1.5.16: {}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Even more dashboard fixes (#10541) - Fix https://github.com/enso-org/cloud-v2/issues/1383 - Fix file download - both on Electron, and in browser - Refresh versions list when uploading neww file version - Fix app crashing when asset is opened in asset panel while switching to Local Backend - Don't show asset id when asset is opened in asset panel, but user is on the Local backend, resulting in the internal Asset ID being shown - Fix drag-n-drop - :warning: `npm run dev` is NOT fixed in this PR - however it should already be fixed in another PR which has already been merged. This needs testing to confirm whether it is fixed though. Other changes: - Add support for "duplicate project" endpoint on Local Backend - Fix downloading project from nested directory on Local Backend (not working) - Refactor more E2E tests to use the "new" architecture - Simplify "new" E2E architecture to minimize boilerplate # Important Notes - When testing downloads, both Electron and browser should be tested as they use completely separate implementations for how files are downloaded.
2024-07-16 12:55:45 +03:00
electron@31.2.0:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@electron/get': 2.0.3
'@types/node': 20.11.21
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
extract-zip: 2.0.1
transitivePeerDependencies:
- supports-color
emoji-regex@8.0.0: {}
emoji-regex@9.2.2: {}
encodeurl@1.0.2: {}
encoding-down@6.3.0:
dependencies:
abstract-leveldown: 6.3.0
inherits: 2.0.4
level-codec: 9.0.2
level-errors: 2.0.1
optional: true
end-of-stream@1.4.4:
dependencies:
once: 1.4.0
entities@2.1.0: {}
entities@4.5.0: {}
env-paths@2.2.1: {}
err-code@2.0.3: {}
errno@0.1.8:
dependencies:
prr: 1.0.1
optional: true
error-ex@1.3.2:
dependencies:
is-arrayish: 0.2.1
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
error-stack-parser-es@0.1.5: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
errs@0.3.2: {}
es-abstract@1.23.3:
dependencies:
array-buffer-byte-length: 1.0.1
arraybuffer.prototype.slice: 1.0.3
available-typed-arrays: 1.0.7
call-bind: 1.0.7
data-view-buffer: 1.0.1
data-view-byte-length: 1.0.1
data-view-byte-offset: 1.0.0
es-define-property: 1.0.0
es-errors: 1.3.0
es-object-atoms: 1.0.0
es-set-tostringtag: 2.0.3
es-to-primitive: 1.2.1
function.prototype.name: 1.1.6
get-intrinsic: 1.2.4
get-symbol-description: 1.0.2
globalthis: 1.0.3
gopd: 1.0.1
has-property-descriptors: 1.0.2
has-proto: 1.0.3
has-symbols: 1.0.3
hasown: 2.0.2
internal-slot: 1.0.7
is-array-buffer: 3.0.4
is-callable: 1.2.7
is-data-view: 1.0.1
is-negative-zero: 2.0.3
is-regex: 1.1.4
is-shared-array-buffer: 1.0.3
is-string: 1.0.7
is-typed-array: 1.1.13
is-weakref: 1.0.2
object-inspect: 1.13.1
object-keys: 1.1.1
object.assign: 4.1.5
regexp.prototype.flags: 1.5.2
safe-array-concat: 1.1.2
safe-regex-test: 1.0.3
string.prototype.trim: 1.2.9
string.prototype.trimend: 1.0.8
string.prototype.trimstart: 1.0.8
typed-array-buffer: 1.0.2
typed-array-byte-length: 1.0.1
typed-array-byte-offset: 1.0.2
typed-array-length: 1.0.6
unbox-primitive: 1.0.2
which-typed-array: 1.1.15
es-define-property@1.0.0:
dependencies:
get-intrinsic: 1.2.4
es-errors@1.3.0: {}
es-iterator-helpers@1.0.19:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-errors: 1.3.0
es-set-tostringtag: 2.0.3
function-bind: 1.1.2
get-intrinsic: 1.2.4
globalthis: 1.0.3
has-property-descriptors: 1.0.2
has-proto: 1.0.3
has-symbols: 1.0.3
internal-slot: 1.0.7
iterator.prototype: 1.1.2
safe-array-concat: 1.1.2
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
es-module-lexer@1.5.4: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
es-object-atoms@1.0.0:
dependencies:
es-errors: 1.3.0
es-set-tostringtag@2.0.3:
dependencies:
get-intrinsic: 1.2.4
has-tostringtag: 1.0.2
hasown: 2.0.2
es-shim-unscopables@1.0.2:
dependencies:
hasown: 2.0.2
es-to-primitive@1.2.1:
dependencies:
is-callable: 1.2.7
is-date-object: 1.0.5
is-symbol: 1.0.4
es6-error@4.1.1:
optional: true
es6-promise@3.3.1: {}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esbuild-plugin-wasm@1.1.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esbuild@0.21.5:
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/aix-ppc64': 0.21.5
'@esbuild/android-arm': 0.21.5
'@esbuild/android-arm64': 0.21.5
'@esbuild/android-x64': 0.21.5
'@esbuild/darwin-arm64': 0.21.5
'@esbuild/darwin-x64': 0.21.5
'@esbuild/freebsd-arm64': 0.21.5
'@esbuild/freebsd-x64': 0.21.5
'@esbuild/linux-arm': 0.21.5
'@esbuild/linux-arm64': 0.21.5
'@esbuild/linux-ia32': 0.21.5
'@esbuild/linux-loong64': 0.21.5
'@esbuild/linux-mips64el': 0.21.5
'@esbuild/linux-ppc64': 0.21.5
'@esbuild/linux-riscv64': 0.21.5
'@esbuild/linux-s390x': 0.21.5
'@esbuild/linux-x64': 0.21.5
'@esbuild/netbsd-x64': 0.21.5
'@esbuild/openbsd-x64': 0.21.5
'@esbuild/sunos-x64': 0.21.5
'@esbuild/win32-arm64': 0.21.5
'@esbuild/win32-ia32': 0.21.5
'@esbuild/win32-x64': 0.21.5
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esbuild@0.23.0:
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@esbuild/aix-ppc64': 0.23.0
'@esbuild/android-arm': 0.23.0
'@esbuild/android-arm64': 0.23.0
'@esbuild/android-x64': 0.23.0
'@esbuild/darwin-arm64': 0.23.0
'@esbuild/darwin-x64': 0.23.0
'@esbuild/freebsd-arm64': 0.23.0
'@esbuild/freebsd-x64': 0.23.0
'@esbuild/linux-arm': 0.23.0
'@esbuild/linux-arm64': 0.23.0
'@esbuild/linux-ia32': 0.23.0
'@esbuild/linux-loong64': 0.23.0
'@esbuild/linux-mips64el': 0.23.0
'@esbuild/linux-ppc64': 0.23.0
'@esbuild/linux-riscv64': 0.23.0
'@esbuild/linux-s390x': 0.23.0
'@esbuild/linux-x64': 0.23.0
'@esbuild/netbsd-x64': 0.23.0
'@esbuild/openbsd-arm64': 0.23.0
'@esbuild/openbsd-x64': 0.23.0
'@esbuild/sunos-x64': 0.23.0
'@esbuild/win32-arm64': 0.23.0
'@esbuild/win32-ia32': 0.23.0
'@esbuild/win32-x64': 0.23.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
escalade@3.2.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
escape-html@1.0.3: {}
escape-string-regexp@1.0.5: {}
escape-string-regexp@4.0.0: {}
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-config-prettier@9.1.0(eslint@9.13.0(jiti@1.21.6)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-plugin-jsdoc@50.4.3(eslint@9.13.0(jiti@1.21.6)):
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@es-joy/jsdoccomment': 0.49.0
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
are-docs-informative: 0.0.2
comment-parser: 1.4.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
escape-string-regexp: 4.0.0
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Align esbuild versions across packages (#11459) Part of #11458 Should get rid of the "magical" CI failure: https://github.com/enso-org/enso/actions/runs/11576387008/job/32225209090#step:7:254
2024-11-06 02:43:27 +03:00
espree: 10.2.0
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
esquery: 1.6.0
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
parse-imports: 2.1.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
spdx-expression-parse: 4.0.0
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
synckit: 0.9.1
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
transitivePeerDependencies:
- supports-color
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-plugin-prettier@5.2.1(@types/eslint@8.56.10)(eslint-config-prettier@9.1.0(eslint@9.13.0(jiti@1.21.6)))(eslint@9.13.0(jiti@1.21.6))(prettier@3.3.2):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prettier: 3.3.2
prettier-linter-helpers: 1.0.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
synckit: 0.9.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/eslint': 8.56.10
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-config-prettier: 9.1.0(eslint@9.13.0(jiti@1.21.6))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
eslint-plugin-react-compiler@19.0.0-beta-8a03594-20241020(eslint@9.13.0(jiti@1.21.6)):
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/parser': 7.25.6
'@babel/plugin-proposal-private-methods': 7.18.6(@babel/core@7.25.2)
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
eslint: 9.13.0(jiti@1.21.6)
hermes-parser: 0.20.1
zod: 3.23.8
zod-validation-error: 3.4.0(zod@3.23.8)
transitivePeerDependencies:
- supports-color
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-plugin-react-hooks@5.0.0(eslint@9.13.0(jiti@1.21.6)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-plugin-react@7.37.1(eslint@9.13.0(jiti@1.21.6)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
array-includes: 3.1.8
array.prototype.findlast: 1.2.5
array.prototype.flatmap: 1.3.2
array.prototype.tosorted: 1.1.4
doctrine: 2.1.0
es-iterator-helpers: 1.0.19
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
estraverse: 5.3.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
hasown: 2.0.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsx-ast-utils: 3.3.5
minimatch: 3.1.2
object.entries: 1.1.8
object.fromentries: 2.0.8
object.values: 1.2.0
prop-types: 15.8.1
resolve: 2.0.0-next.5
semver: 6.3.1
string.prototype.matchall: 4.0.11
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
string.prototype.repeat: 1.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-plugin-vue@9.29.1(eslint@9.13.0(jiti@1.21.6)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint-community/eslint-utils': 4.4.0(eslint@9.13.0(jiti@1.21.6))
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
globals: 13.24.0
natural-compare: 1.4.0
nth-check: 2.1.1
postcss-selector-parser: 6.1.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
vue-eslint-parser: 9.4.3(eslint@9.13.0(jiti@1.21.6))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xml-name-validator: 4.0.0
transitivePeerDependencies:
- supports-color
eslint-scope@7.2.2:
dependencies:
esrecurse: 4.3.0
estraverse: 5.3.0
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-scope@8.1.0:
dependencies:
esrecurse: 4.3.0
estraverse: 5.3.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
eslint-visitor-keys@3.4.3: {}
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-visitor-keys@4.1.0: {}
eslint@9.13.0(jiti@1.21.6):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@eslint-community/eslint-utils': 4.4.0(eslint@9.13.0(jiti@1.21.6))
'@eslint-community/regexpp': 4.11.0
'@eslint/config-array': 0.18.0
'@eslint/core': 0.7.0
'@eslint/eslintrc': 3.1.0
'@eslint/js': 9.13.0
'@eslint/plugin-kit': 0.2.1
'@humanfs/node': 0.16.5
'@humanwhocodes/module-importer': 1.0.1
'@humanwhocodes/retry': 0.3.1
'@types/estree': 1.0.6
'@types/json-schema': 7.0.15
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ajv: 6.12.6
chalk: 4.1.2
cross-spawn: 7.0.3
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
escape-string-regexp: 4.0.0
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint-scope: 8.1.0
eslint-visitor-keys: 4.1.0
espree: 10.2.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esquery: 1.6.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esutils: 2.0.3
fast-deep-equal: 3.1.3
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
file-entry-cache: 8.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
find-up: 5.0.0
glob-parent: 6.0.2
ignore: 5.3.1
imurmurhash: 0.1.4
is-glob: 4.0.3
json-stable-stringify-without-jsonify: 1.0.1
lodash.merge: 4.6.2
minimatch: 3.1.2
natural-compare: 1.4.0
optionator: 0.9.4
text-table: 0.2.0
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
optionalDependencies:
jiti: 1.21.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
espree@10.2.0:
dependencies:
acorn: 8.12.0
acorn-jsx: 5.3.2(acorn@8.12.0)
eslint-visitor-keys: 4.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
espree@9.6.1:
dependencies:
acorn: 8.12.0
acorn-jsx: 5.3.2(acorn@8.12.0)
eslint-visitor-keys: 3.4.3
esprima@4.0.1: {}
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
esquery@1.6.0:
dependencies:
estraverse: 5.3.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esrecurse@4.3.0:
dependencies:
estraverse: 5.3.0
estraverse@5.3.0: {}
estree-walker@2.0.2: {}
estree-walker@3.0.3:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/estree': 1.0.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
esutils@2.0.3: {}
event-pubsub@4.3.0: {}
event-target-shim@6.0.2: {}
events@3.3.0: {}
execa@8.0.1:
dependencies:
cross-spawn: 7.0.3
get-stream: 8.0.1
human-signals: 5.0.0
is-stream: 3.0.0
merge-stream: 2.0.0
npm-run-path: 5.3.0
onetime: 6.0.0
signal-exit: 4.1.0
strip-final-newline: 3.0.0
exif-parser@0.1.12: {}
expand-template@2.0.3: {}
extend-shallow@2.0.1:
dependencies:
is-extendable: 0.1.1
extend@3.0.2: {}
extract-zip@2.0.1:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-stream: 5.2.0
yauzl: 2.10.0
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/yauzl': 2.10.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
extsprintf@1.3.0: {}
extsprintf@1.4.1: {}
fast-base64-decode@1.0.0: {}
fast-check@3.19.0:
dependencies:
pure-rand: 6.1.0
fast-deep-equal@3.1.3: {}
fast-diff@1.3.0: {}
fast-glob@3.3.2:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@nodelib/fs.stat': 2.0.5
'@nodelib/fs.walk': 1.2.8
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
glob-parent: 5.1.2
merge2: 1.4.1
micromatch: 4.0.5
fast-json-stable-stringify@2.1.0: {}
fast-levenshtein@2.0.6: {}
fast-safe-stringify@2.1.1: {}
fastq@1.17.1:
dependencies:
reusify: 1.0.4
fd-slicer@1.1.0:
dependencies:
pend: 1.2.0
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
file-entry-cache@8.0.0:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
flat-cache: 4.0.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
file-type@3.9.0: {}
filelist@1.0.4:
dependencies:
minimatch: 5.1.6
fill-range@7.0.1:
dependencies:
to-regex-range: 5.0.1
finalhandler@1.1.2:
dependencies:
debug: 2.6.9
encodeurl: 1.0.2
escape-html: 1.0.3
on-finished: 2.3.0
parseurl: 1.3.3
statuses: 1.5.0
unpipe: 1.0.0
transitivePeerDependencies:
- supports-color
find-up@5.0.0:
dependencies:
locate-path: 6.0.0
path-exists: 4.0.0
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
flat-cache@4.0.1:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
flatted: 3.3.1
keyv: 4.5.4
flatted@3.3.1: {}
flexsearch@0.7.21: {}
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
floating-vue@2.0.0(vue@3.5.2(typescript@5.5.3)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@floating-ui/dom': 1.1.1
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
vue-resize: 2.0.0-alpha.1(vue@3.5.2(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
for-each@0.3.3:
dependencies:
is-callable: 1.2.7
foreground-child@3.2.1:
dependencies:
cross-spawn: 7.0.3
signal-exit: 4.1.0
forever-agent@0.6.1: {}
form-data@2.3.3:
dependencies:
asynckit: 0.4.0
combined-stream: 1.0.8
mime-types: 2.1.35
form-data@3.0.1:
dependencies:
asynckit: 0.4.0
combined-stream: 1.0.8
mime-types: 2.1.35
form-data@4.0.0:
dependencies:
asynckit: 0.4.0
combined-stream: 1.0.8
mime-types: 2.1.35
format-util@1.0.5: {}
Setup Screen Improvements (#10844)
2024-09-05 19:11:02 +03:00
framer-motion@11.3.0(@emotion/is-prop-valid@1.3.0)(react-dom@18.3.1(react@18.3.1))(react@18.3.1):
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
dependencies:
tslib: 2.6.3
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@emotion/is-prop-valid': 1.3.0
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-constants@1.0.0: {}
fs-extra@10.1.0:
dependencies:
graceful-fs: 4.2.11
jsonfile: 6.1.0
universalify: 2.0.1
fs-extra@11.2.0:
dependencies:
graceful-fs: 4.2.11
jsonfile: 6.1.0
universalify: 2.0.1
fs-extra@7.0.1:
dependencies:
graceful-fs: 4.2.11
jsonfile: 4.0.0
universalify: 0.1.2
fs-extra@8.1.0:
dependencies:
graceful-fs: 4.2.11
jsonfile: 4.0.0
universalify: 0.1.2
fs-extra@9.1.0:
dependencies:
at-least-node: 1.0.0
graceful-fs: 4.2.11
jsonfile: 6.1.0
universalify: 2.0.1
fs-minipass@2.1.0:
dependencies:
minipass: 3.3.6
fs.realpath@1.0.0: {}
fsevents@2.3.2:
optional: true
fsevents@2.3.3:
optional: true
function-bind@1.1.2: {}
function.prototype.name@1.1.6:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
functions-have-names: 1.2.3
functions-have-names@1.2.3: {}
gensync@1.0.0-beta.2: {}
get-caller-file@2.0.5: {}
get-func-name@2.0.2: {}
get-intrinsic@1.2.4:
dependencies:
es-errors: 1.3.0
function-bind: 1.1.2
has-proto: 1.0.3
has-symbols: 1.0.3
hasown: 2.0.2
get-stdin@8.0.0: {}
get-stream@2.3.1:
dependencies:
object-assign: 4.1.1
pinkie-promise: 2.0.1
get-stream@5.2.0:
dependencies:
pump: 3.0.0
get-stream@8.0.1: {}
get-symbol-description@1.0.2:
dependencies:
call-bind: 1.0.7
es-errors: 1.3.0
get-intrinsic: 1.2.4
get-tsconfig@4.7.5:
dependencies:
resolve-pkg-maps: 1.0.0
getpass@0.1.7:
dependencies:
assert-plus: 1.0.0
github-from-package@0.0.0: {}
glob-parent@5.1.2:
dependencies:
is-glob: 4.0.3
glob-parent@6.0.2:
dependencies:
is-glob: 4.0.3
glob@10.4.2:
dependencies:
foreground-child: 3.2.1
jackspeak: 3.4.0
minimatch: 9.0.5
minipass: 7.1.2
package-json-from-dist: 1.0.0
path-scurry: 1.11.1
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
glob@11.0.0:
dependencies:
foreground-child: 3.2.1
jackspeak: 4.0.1
minimatch: 10.0.1
minipass: 7.1.2
package-json-from-dist: 1.0.0
path-scurry: 2.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
glob@7.2.3:
dependencies:
fs.realpath: 1.0.0
inflight: 1.0.6
inherits: 2.0.4
minimatch: 3.1.2
once: 1.4.0
path-is-absolute: 1.0.1
global-agent@3.0.0:
dependencies:
boolean: 3.2.0
es6-error: 4.1.1
matcher: 3.0.0
roarr: 2.15.4
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
serialize-error: 7.0.1
optional: true
global@4.4.0:
dependencies:
min-document: 2.19.0
process: 0.11.10
globals@11.12.0: {}
globals@13.24.0:
dependencies:
type-fest: 0.20.2
globals@14.0.0: {}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
globals@15.8.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
globalthis@1.0.3:
dependencies:
define-properties: 1.2.1
globby@13.2.2:
dependencies:
dir-glob: 3.0.1
fast-glob: 3.3.2
ignore: 5.3.1
merge2: 1.4.1
slash: 4.0.0
gopd@1.0.1:
dependencies:
get-intrinsic: 1.2.4
got@11.8.6:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@sindresorhus/is': 4.6.0
'@szmarczak/http-timer': 4.0.6
'@types/cacheable-request': 6.0.3
'@types/responselike': 1.0.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cacheable-lookup: 5.0.4
cacheable-request: 7.0.4
decompress-response: 6.0.0
http2-wrapper: 1.0.3
lowercase-keys: 2.0.0
p-cancelable: 2.1.1
responselike: 2.0.1
graceful-fs@4.2.11: {}
graphemer@1.4.0: {}
gray-matter@4.0.3:
dependencies:
js-yaml: 3.14.1
kind-of: 6.0.3
section-matter: 1.0.0
strip-bom-string: 1.0.0
har-schema@2.0.0: {}
har-validator@5.1.5:
dependencies:
ajv: 6.12.6
har-schema: 2.0.0
has-bigints@1.0.2: {}
has-flag@3.0.0: {}
has-flag@4.0.0: {}
has-property-descriptors@1.0.2:
dependencies:
es-define-property: 1.0.0
has-proto@1.0.3: {}
has-symbols@1.0.3: {}
has-tostringtag@1.0.2:
dependencies:
has-symbols: 1.0.3
hash-sum@2.0.0: {}
hash-wasm@4.11.0: {}
hasown@2.0.2:
dependencies:
function-bind: 1.1.2
he@1.2.0: {}
header-case@2.0.4:
dependencies:
capital-case: 1.0.4
tslib: 2.6.3
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
hermes-estree@0.20.1: {}
hermes-parser@0.20.1:
dependencies:
hermes-estree: 0.20.1
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
histoire@0.17.17(@types/node@22.9.0)(lightningcss@1.25.1)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@akryum/tinypool': 0.3.1
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@histoire/app': 0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
'@histoire/controls': 0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
'@histoire/shared': 0.17.17(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@histoire/vendors': 0.17.17
'@types/flexsearch': 0.7.6
'@types/markdown-it': 12.2.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
birpc: 0.1.1
change-case: 4.1.2
chokidar: 3.6.0
connect: 3.7.0
defu: 6.1.4
diacritics: 1.3.0
flexsearch: 0.7.21
fs-extra: 10.1.0
globby: 13.2.2
gray-matter: 4.0.3
jiti: 1.21.6
jsdom: 24.1.0
markdown-it: 12.3.2
markdown-it-anchor: 8.6.7(@types/markdown-it@12.2.3)(markdown-it@12.3.2)
markdown-it-attrs: 4.1.6(markdown-it@12.3.2)
markdown-it-emoji: 2.0.2
micromatch: 4.0.5
mrmime: 1.0.1
pathe: 1.1.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sade: 1.8.1
shiki-es: 0.2.0
sirv: 2.0.4
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
vite-node: 0.34.7(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@types/node'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- bufferutil
- canvas
- less
- lightningcss
- sass
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
- sass-embedded
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- stylus
- sugarss
- supports-color
- terser
- utf-8-validate
hoist-non-react-statics@3.3.2:
dependencies:
react-is: 16.13.1
hookable@5.5.3: {}
hosted-git-info@2.8.9: {}
hosted-git-info@4.1.0:
dependencies:
lru-cache: 6.0.0
html-encoding-sniffer@4.0.0:
dependencies:
whatwg-encoding: 3.1.1
html-escaper@2.0.2: {}
html-tags@3.3.1: {}
htmlparser2@8.0.2:
dependencies:
domelementtype: 2.3.0
domhandler: 5.0.3
domutils: 3.1.0
entities: 4.5.0
http-cache-semantics@4.1.1: {}
http-errors@2.0.0:
dependencies:
depd: 2.0.0
inherits: 2.0.4
setprototypeof: 1.2.0
statuses: 2.0.1
toidentifier: 1.0.1
http-proxy-agent@5.0.0:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@tootallnate/once': 2.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
agent-base: 6.0.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
http-proxy-agent@7.0.2:
dependencies:
agent-base: 7.1.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
http-signature@1.2.0:
dependencies:
assert-plus: 1.0.0
jsprim: 1.4.2
sshpk: 1.18.0
http2-wrapper@1.0.3:
dependencies:
quick-lru: 5.1.1
resolve-alpn: 1.2.1
https-proxy-agent@5.0.1:
dependencies:
agent-base: 6.0.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
https-proxy-agent@7.0.5:
dependencies:
agent-base: 7.1.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
human-signals@5.0.0: {}
iconv-corefoundation@1.1.7:
dependencies:
cli-truncate: 2.1.0
node-addon-api: 1.7.2
optional: true
iconv-lite@0.4.24:
dependencies:
safer-buffer: 2.1.2
iconv-lite@0.6.3:
dependencies:
safer-buffer: 2.1.2
idb-keyval@6.2.1: {}
ieee754@1.2.1: {}
ignore@5.3.1: {}
image-size@0.5.5: {}
immediate@3.0.6: {}
immediate@3.3.0:
optional: true
import-fresh@3.3.0:
dependencies:
parent-module: 1.0.1
resolve-from: 4.0.0
imurmurhash@0.1.4: {}
indefinitely-typed@1.1.0:
dependencies:
fs-extra: 7.0.1
minimist: 1.2.8
inflight@1.0.6:
dependencies:
once: 1.4.0
wrappy: 1.0.2
inherits@2.0.4: {}
ini@1.3.8: {}
MFA (#10875) * Draft checkbox component * Fixes in Setup Page * Invite Users * Add usergroup setup after subscription * Fix comments * Refetch Interval + Feature Toggles * Fix lint * Address issues * Fix Dialog * Assign users to the user group * Use transitions to navigate between steps * Small fixes * Improve styling for scrollbars * Fix typescript * OTP input * Fix setup logic * Show Setup dialog only for admins * Add otp * OTP input * 2FA settings section * Small improvements * Fixes * Small fixes * Remove w-full * TOTP at login * Fixes in 2FA * Fixes in types * Fix totp * Merge fixes * Merge fixes x2 * Merge fixes x2 * Fix types * Fix types * Fix cancel button * Fix reset button * Fix types * Fix prettier * Fix prettier * Fix lint * Fix lint * Fix control * Address prettier * Fix MFA mock * Fix sign in message * Fix tests * Address CR * Fix types
2024-09-13 16:00:31 +03:00
input-otp@1.2.4(react-dom@18.3.1(react@18.3.1))(react@18.3.1):
dependencies:
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
install@0.13.0: {}
internal-slot@1.0.7:
dependencies:
es-errors: 1.3.0
hasown: 2.0.2
side-channel: 1.0.6
internmap@2.0.3: {}
intl-messageformat@10.5.14:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@formatjs/ecma402-abstract': 2.0.0
'@formatjs/fast-memoize': 2.2.0
'@formatjs/icu-messageformat-parser': 2.7.8
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tslib: 2.6.3
ip-regex@1.0.3: {}
is-array-buffer@3.0.4:
dependencies:
call-bind: 1.0.7
get-intrinsic: 1.2.4
is-arrayish@0.2.1: {}
is-arrayish@0.3.2: {}
is-async-function@2.0.0:
dependencies:
has-tostringtag: 1.0.2
is-bigint@1.0.4:
dependencies:
has-bigints: 1.0.2
is-binary-path@2.1.0:
dependencies:
binary-extensions: 2.3.0
is-boolean-object@1.1.2:
dependencies:
call-bind: 1.0.7
has-tostringtag: 1.0.2
is-callable@1.2.7: {}
is-ci@3.0.1:
dependencies:
ci-info: 3.9.0
is-core-module@2.13.1:
dependencies:
hasown: 2.0.2
is-data-view@1.0.1:
dependencies:
is-typed-array: 1.1.13
is-date-object@1.0.5:
dependencies:
has-tostringtag: 1.0.2
is-docker@3.0.0: {}
is-extendable@0.1.1: {}
is-extglob@2.1.1: {}
is-finalizationregistry@1.0.2:
dependencies:
call-bind: 1.0.7
is-fullwidth-code-point@3.0.0: {}
is-function@1.0.2: {}
is-generator-function@1.0.10:
dependencies:
has-tostringtag: 1.0.2
is-glob@4.0.3:
dependencies:
is-extglob: 2.1.1
is-inside-container@1.0.0:
dependencies:
is-docker: 3.0.0
is-map@2.0.3: {}
is-negative-zero@2.0.3: {}
is-network-error@1.1.0: {}
is-number-object@1.0.7:
dependencies:
has-tostringtag: 1.0.2
is-number@7.0.0: {}
is-potential-custom-element-name@1.0.1: {}
is-regex@1.1.4:
dependencies:
call-bind: 1.0.7
has-tostringtag: 1.0.2
is-set@2.0.3: {}
is-shared-array-buffer@1.0.3:
dependencies:
call-bind: 1.0.7
is-stream@3.0.0: {}
is-string@1.0.7:
dependencies:
has-tostringtag: 1.0.2
is-symbol@1.0.4:
dependencies:
has-symbols: 1.0.3
is-typed-array@1.1.13:
dependencies:
which-typed-array: 1.1.15
is-typedarray@1.0.0: {}
is-url@1.2.4: {}
is-weakmap@2.0.2: {}
is-weakref@1.0.2:
dependencies:
call-bind: 1.0.7
is-weakset@2.0.3:
dependencies:
call-bind: 1.0.7
get-intrinsic: 1.2.4
is-what@4.1.16: {}
is-wsl@3.1.0:
dependencies:
is-inside-container: 1.0.0
isarray@1.0.0: {}
isarray@2.0.5: {}
isbinaryfile@4.0.10: {}
isbinaryfile@5.0.2: {}
isexe@2.0.0: {}
isomorphic-fetch@3.0.0:
dependencies:
node-fetch: 2.7.0
whatwg-fetch: 3.6.20
transitivePeerDependencies:
- encoding
isomorphic-unfetch@3.1.0:
dependencies:
node-fetch: 2.7.0
unfetch: 4.2.0
transitivePeerDependencies:
- encoding
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
isomorphic-ws@5.0.0(ws@8.18.0):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws: 8.18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
isomorphic.js@0.2.5: {}
isstream@0.1.2: {}
istanbul-lib-coverage@3.2.2: {}
istanbul-lib-report@3.0.1:
dependencies:
istanbul-lib-coverage: 3.2.2
make-dir: 4.0.0
supports-color: 7.2.0
istanbul-lib-source-maps@5.0.5:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/trace-mapping': 0.3.25
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
istanbul-lib-coverage: 3.2.2
transitivePeerDependencies:
- supports-color
istanbul-reports@3.1.7:
dependencies:
html-escaper: 2.0.2
istanbul-lib-report: 3.0.1
iterator.prototype@1.1.2:
dependencies:
define-properties: 1.2.1
get-intrinsic: 1.2.4
has-symbols: 1.0.3
reflect.getprototypeof: 1.0.6
set-function-name: 2.0.2
jackspeak@3.4.0:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@isaacs/cliui': 8.0.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@pkgjs/parseargs': 0.11.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
jackspeak@4.0.1:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@isaacs/cliui': 8.0.2
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@pkgjs/parseargs': 0.11.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jake@10.9.1:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
async: 3.2.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
chalk: 4.1.2
filelist: 1.0.4
minimatch: 3.1.2
jimp@0.2.28:
dependencies:
bignumber.js: 2.4.0
bmp-js: 0.0.3
es6-promise: 3.3.1
exif-parser: 0.1.12
file-type: 3.9.0
jpeg-js: 0.2.0
load-bmfont: 1.4.1
mime: 1.6.0
mkdirp: 0.5.1
pixelmatch: 4.0.2
pngjs: 3.4.0
read-chunk: 1.0.1
request: 2.88.2
stream-to-buffer: 0.1.0
tinycolor2: 1.6.0
url-regex: 3.2.0
jiti@1.21.6: {}
jpeg-js@0.1.2: {}
jpeg-js@0.2.0: {}
js-beautify@1.15.1:
dependencies:
config-chain: 1.1.13
editorconfig: 1.0.4
glob: 10.4.2
js-cookie: 3.0.5
nopt: 7.2.1
js-cookie@2.2.1: {}
js-cookie@3.0.5: {}
js-message@1.0.5: {}
js-queue@2.0.0:
dependencies:
easy-stack: 1.0.1
js-tokens@4.0.0: {}
js-tokens@9.0.0: {}
js-yaml@3.14.1:
dependencies:
argparse: 1.0.10
esprima: 4.0.1
js-yaml@4.1.0:
dependencies:
argparse: 2.0.1
jsbn@0.1.1: {}
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
jsdoc-type-pratt-parser@4.1.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsdom@24.1.0:
dependencies:
cssstyle: 4.0.1
data-urls: 5.0.0
decimal.js: 10.4.3
form-data: 4.0.0
html-encoding-sniffer: 4.0.0
http-proxy-agent: 7.0.2
https-proxy-agent: 7.0.5
is-potential-custom-element-name: 1.0.1
nwsapi: 2.2.10
parse5: 7.1.2
rrweb-cssom: 0.7.1
saxes: 6.0.0
symbol-tree: 3.2.4
tough-cookie: 4.1.4
w3c-xmlserializer: 5.0.0
webidl-conversions: 7.0.0
whatwg-encoding: 3.1.1
whatwg-mimetype: 4.0.0
whatwg-url: 14.0.0
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws: 8.18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xml-name-validator: 5.0.0
transitivePeerDependencies:
- bufferutil
- supports-color
- utf-8-validate
jsesc@2.5.2: {}
json-buffer@3.0.1: {}
json-parse-better-errors@1.0.2: {}
json-schema-faker@0.5.6:
dependencies:
json-schema-ref-parser: 6.1.0
jsonpath-plus: 7.2.0
json-schema-ref-parser@6.1.0:
dependencies:
call-me-maybe: 1.0.2
js-yaml: 3.14.1
ono: 4.0.11
json-schema-traverse@0.4.1: {}
json-schema-traverse@1.0.0: {}
json-schema@0.4.0: {}
json-stable-stringify-without-jsonify@1.0.1: {}
json-stringify-safe@5.0.1: {}
json5@2.2.3: {}
jsonfile@4.0.0:
optionalDependencies:
graceful-fs: 4.2.11
jsonfile@6.1.0:
dependencies:
universalify: 2.0.1
optionalDependencies:
graceful-fs: 4.2.11
jsonpath-plus@7.2.0: {}
jsprim@1.4.2:
dependencies:
assert-plus: 1.0.0
extsprintf: 1.3.0
json-schema: 0.4.0
verror: 1.10.0
jsx-ast-utils@3.3.5:
dependencies:
array-includes: 3.1.8
array.prototype.flat: 1.3.2
object.assign: 4.1.5
object.values: 1.2.0
keyv@4.5.4:
dependencies:
json-buffer: 3.0.1
kind-of@6.0.3: {}
kolorist@1.8.0: {}
launch-editor@2.8.0:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
shell-quote: 1.8.1
lazy-val@1.0.5: {}
lazystream@1.0.1:
dependencies:
readable-stream: 2.3.8
level-codec@9.0.2:
dependencies:
buffer: 5.7.1
optional: true
level-concat-iterator@2.0.1:
optional: true
level-errors@2.0.1:
dependencies:
errno: 0.1.8
optional: true
level-iterator-stream@4.0.2:
dependencies:
inherits: 2.0.4
readable-stream: 3.6.2
xtend: 4.0.2
optional: true
level-js@5.0.2:
dependencies:
abstract-leveldown: 6.2.3
buffer: 5.7.1
inherits: 2.0.4
ltgt: 2.2.1
optional: true
level-packager@5.1.1:
dependencies:
encoding-down: 6.3.0
levelup: 4.4.0
optional: true
level-supports@1.0.1:
dependencies:
xtend: 4.0.2
optional: true
level@6.0.1:
dependencies:
level-js: 5.0.2
level-packager: 5.1.1
leveldown: 5.6.0
optional: true
leveldown@5.6.0:
dependencies:
abstract-leveldown: 6.2.3
napi-macros: 2.0.0
node-gyp-build: 4.1.1
optional: true
levelup@4.4.0:
dependencies:
deferred-leveldown: 5.3.0
level-errors: 2.0.1
level-iterator-stream: 4.0.2
level-supports: 1.0.1
xtend: 4.0.2
optional: true
levn@0.4.1:
dependencies:
prelude-ls: 1.2.1
type-check: 0.4.0
lexical@0.16.0: {}
lib0@0.2.94:
dependencies:
isomorphic.js: 0.2.5
lie@3.1.1:
dependencies:
immediate: 3.0.6
lightningcss-darwin-arm64@1.25.1:
optional: true
lightningcss-darwin-x64@1.25.1:
optional: true
lightningcss-freebsd-x64@1.25.1:
optional: true
lightningcss-linux-arm-gnueabihf@1.25.1:
optional: true
lightningcss-linux-arm64-gnu@1.25.1:
optional: true
lightningcss-linux-arm64-musl@1.25.1:
optional: true
lightningcss-linux-x64-gnu@1.25.1:
optional: true
lightningcss-linux-x64-musl@1.25.1:
optional: true
lightningcss-win32-x64-msvc@1.25.1:
optional: true
lightningcss@1.25.1:
dependencies:
detect-libc: 1.0.3
optionalDependencies:
lightningcss-darwin-arm64: 1.25.1
lightningcss-darwin-x64: 1.25.1
lightningcss-freebsd-x64: 1.25.1
lightningcss-linux-arm-gnueabihf: 1.25.1
lightningcss-linux-arm64-gnu: 1.25.1
lightningcss-linux-arm64-musl: 1.25.1
lightningcss-linux-x64-gnu: 1.25.1
lightningcss-linux-x64-musl: 1.25.1
lightningcss-win32-x64-msvc: 1.25.1
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
optional: true
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lilconfig@2.1.0: {}
lilconfig@3.1.2: {}
lines-and-columns@1.2.4: {}
linkify-it@3.0.3:
dependencies:
uc.micro: 1.0.6
load-bmfont@1.4.1:
dependencies:
buffer-equal: 0.0.1
mime: 1.6.0
parse-bmfont-ascii: 1.0.6
parse-bmfont-binary: 1.0.6
parse-bmfont-xml: 1.1.6
phin: 2.9.3
xhr: 2.6.0
xtend: 4.0.2
load-json-file@4.0.0:
dependencies:
graceful-fs: 4.2.11
parse-json: 4.0.0
pify: 3.0.0
strip-bom: 3.0.0
local-pkg@0.5.0:
dependencies:
mlly: 1.7.1
pkg-types: 1.1.2
localforage@1.10.0:
dependencies:
lie: 3.1.1
locate-path@6.0.0:
dependencies:
p-locate: 5.0.0
lodash.debounce@4.0.8: {}
lodash.defaults@4.2.0: {}
lodash.difference@4.5.0: {}
lodash.flatten@4.4.0: {}
lodash.isplainobject@4.0.6: {}
lodash.merge@4.6.2: {}
lodash.union@4.6.0: {}
lodash@4.17.21: {}
loose-envify@1.4.0:
dependencies:
js-tokens: 4.0.0
loupe@2.3.7:
dependencies:
get-func-name: 2.0.2
lower-case@2.0.2:
dependencies:
tslib: 2.6.3
lowercase-keys@2.0.0: {}
lru-cache@10.3.0: {}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
lru-cache@11.0.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lru-cache@5.1.1:
dependencies:
yallist: 3.1.1
lru-cache@6.0.0:
dependencies:
yallist: 4.0.0
ltgt@2.2.1:
optional: true
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
magic-string@0.30.11:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/sourcemap-codec': 1.5.0
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
magicast@0.3.4:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/parser': 7.25.6
'@babel/types': 7.25.6
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
source-map-js: 1.2.0
make-dir@4.0.0:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
markdown-it-anchor@8.6.7(@types/markdown-it@12.2.3)(markdown-it@12.3.2):
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/markdown-it': 12.2.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
markdown-it: 12.3.2
markdown-it-attrs@4.1.6(markdown-it@12.3.2):
dependencies:
markdown-it: 12.3.2
markdown-it-emoji@2.0.2: {}
markdown-it@12.3.2:
dependencies:
argparse: 2.0.1
entities: 2.1.0
linkify-it: 3.0.3
mdurl: 1.0.1
uc.micro: 1.0.6
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
marked@14.1.3: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
matcher@3.0.0:
dependencies:
escape-string-regexp: 4.0.0
optional: true
mdurl@1.0.1: {}
media-typer@0.3.0: {}
memorystream@0.3.1: {}
merge-stream@2.0.0: {}
merge2@1.4.1: {}
micromatch@4.0.5:
dependencies:
braces: 3.0.2
picomatch: 2.3.1
mime-db@1.52.0: {}
mime-types@2.1.35:
dependencies:
mime-db: 1.52.0
mime@1.6.0: {}
mime@2.6.0: {}
mimic-fn@4.0.0: {}
mimic-response@1.0.1: {}
mimic-response@3.1.0: {}
min-document@2.19.0:
dependencies:
dom-walk: 0.1.2
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
minimatch@10.0.1:
dependencies:
brace-expansion: 2.0.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
minimatch@3.1.2:
dependencies:
brace-expansion: 1.1.11
minimatch@5.1.6:
dependencies:
brace-expansion: 2.0.1
minimatch@9.0.1:
dependencies:
brace-expansion: 2.0.1
minimatch@9.0.5:
dependencies:
brace-expansion: 2.0.1
minimist@0.0.8: {}
minimist@1.2.8: {}
minipass@3.3.6:
dependencies:
yallist: 4.0.0
minipass@4.2.8: {}
minipass@5.0.0: {}
minipass@7.1.2: {}
minizlib@2.1.2:
dependencies:
minipass: 3.3.6
yallist: 4.0.0
mitt@3.0.1: {}
mkcert@3.2.0:
dependencies:
commander: 11.1.0
node-forge: 1.3.1
mkdirp-classic@0.5.3: {}
mkdirp@0.5.1:
dependencies:
minimist: 0.0.8
mkdirp@0.5.6:
dependencies:
minimist: 1.2.8
mkdirp@1.0.4: {}
mlly@1.7.1:
dependencies:
acorn: 8.12.0
pathe: 1.1.2
pkg-types: 1.1.2
ufo: 1.5.3
monaco-editor@0.48.0: {}
moo@0.5.2: {}
mri@1.2.0: {}
mrmime@1.0.1: {}
mrmime@2.0.0: {}
ms@2.0.0: {}
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
ms@2.1.3: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
muggle-string@0.4.1: {}
murmurhash@2.0.1: {}
mz@2.7.0:
dependencies:
any-promise: 1.3.0
object-assign: 4.1.1
thenify-all: 1.6.0
nanoid@3.3.7: {}
napi-build-utils@1.0.2: {}
napi-macros@2.0.0:
optional: true
natural-compare@1.4.0: {}
nearley@2.20.1:
dependencies:
commander: 2.20.3
moo: 0.5.2
railroad-diagrams: 1.0.0
randexp: 0.4.6
nice-try@1.0.5: {}
no-case@3.0.4:
dependencies:
lower-case: 2.0.2
tslib: 2.6.3
node-abi@3.65.0:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
node-addon-api@1.7.2:
optional: true
node-addon-api@5.1.0: {}
node-fetch@2.7.0:
dependencies:
whatwg-url: 5.0.0
node-forge@1.3.1: {}
node-gyp-build@4.1.1:
optional: true
node-ipc@9.1.1:
dependencies:
event-pubsub: 4.3.0
js-message: 1.0.5
js-queue: 2.0.0
Setup Screen Improvements (#10844)
2024-09-05 19:11:02 +03:00
node-releases@2.0.18: {}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
nopt@7.2.1:
dependencies:
abbrev: 2.0.0
normalize-package-data@2.5.0:
dependencies:
hosted-git-info: 2.8.9
resolve: 1.22.8
semver: 5.7.2
validate-npm-package-license: 3.0.4
normalize-path@3.0.0: {}
normalize-url@6.1.0: {}
npm-run-all@4.1.5:
dependencies:
ansi-styles: 3.2.1
chalk: 2.4.2
cross-spawn: 6.0.5
memorystream: 0.3.1
minimatch: 3.1.2
pidtree: 0.3.1
read-pkg: 3.0.0
shell-quote: 1.8.1
string.prototype.padend: 3.1.6
npm-run-path@5.3.0:
dependencies:
path-key: 4.0.0
nth-check@2.1.1:
dependencies:
boolbase: 1.0.0
nwsapi@2.2.10: {}
oauth-sign@0.9.0: {}
object-assign@4.1.1: {}
object-hash@3.0.0: {}
object-inspect@1.13.1: {}
object-keys@1.1.1: {}
object.assign@4.1.5:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
has-symbols: 1.0.3
object-keys: 1.1.1
object.entries@1.1.8:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-object-atoms: 1.0.0
object.fromentries@2.0.8:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-object-atoms: 1.0.0
object.values@1.2.0:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-object-atoms: 1.0.0
on-finished@2.3.0:
dependencies:
ee-first: 1.1.1
on-finished@2.4.1:
dependencies:
ee-first: 1.1.1
once@1.4.0:
dependencies:
wrappy: 1.0.2
onetime@6.0.0:
dependencies:
mimic-fn: 4.0.0
ono@4.0.11:
dependencies:
format-util: 1.0.5
open@10.1.0:
dependencies:
default-browser: 5.2.1
define-lazy-prop: 3.0.0
is-inside-container: 1.0.0
is-wsl: 3.1.0
opener@1.5.2: {}
optionator@0.9.4:
dependencies:
deep-is: 0.1.4
fast-levenshtein: 2.0.6
levn: 0.4.1
prelude-ls: 1.2.1
type-check: 0.4.0
word-wrap: 1.2.5
p-cancelable@2.1.1: {}
p-limit@3.1.0:
dependencies:
yocto-queue: 0.1.0
p-limit@5.0.0:
dependencies:
yocto-queue: 1.1.1
p-locate@5.0.0:
dependencies:
p-limit: 3.1.0
package-json-from-dist@1.0.0: {}
param-case@3.0.4:
dependencies:
dot-case: 3.0.4
tslib: 2.6.3
parent-module@1.0.1:
dependencies:
callsites: 3.1.0
parse-bmfont-ascii@1.0.6: {}
parse-bmfont-binary@1.0.6: {}
parse-bmfont-xml@1.1.6:
dependencies:
xml-parse-from-string: 1.0.1
xml2js: 0.5.0
parse-headers@2.0.5: {}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
parse-imports@2.1.1:
dependencies:
es-module-lexer: 1.5.4
slashes: 3.0.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
parse-json@4.0.0:
dependencies:
error-ex: 1.3.2
json-parse-better-errors: 1.0.2
parse-png@1.1.2:
dependencies:
pngjs: 3.4.0
parse5@7.1.2:
dependencies:
entities: 4.5.0
parseurl@1.3.3: {}
partysocket@1.0.1:
dependencies:
event-target-shim: 6.0.2
pascal-case@3.1.2:
dependencies:
no-case: 3.0.4
tslib: 2.6.3
path-browserify@1.0.1: {}
path-case@3.0.4:
dependencies:
dot-case: 3.0.4
tslib: 2.6.3
path-exists@4.0.0: {}
path-is-absolute@1.0.1: {}
path-key@2.0.1: {}
path-key@3.1.1: {}
path-key@4.0.0: {}
path-parse@1.0.7: {}
path-scurry@1.11.1:
dependencies:
lru-cache: 10.3.0
minipass: 7.1.2
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
path-scurry@2.0.0:
dependencies:
lru-cache: 11.0.0
minipass: 7.1.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
path-type@3.0.0:
dependencies:
pify: 3.0.0
path-type@4.0.0: {}
pathe@1.1.2: {}
pathval@1.1.1: {}
pend@1.2.0: {}
perfect-debounce@1.0.0: {}
performance-now@2.1.0: {}
phin@2.9.3: {}
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
picocolors@1.1.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
picomatch@2.3.1: {}
pidtree@0.3.1: {}
pify@2.3.0: {}
pify@3.0.0: {}
pinkie-promise@2.0.1:
dependencies:
pinkie: 2.0.4
pinkie@2.0.4: {}
pirates@4.0.6: {}
pixelmatch@4.0.2:
dependencies:
pngjs: 3.4.0
pkg-types@1.1.2:
dependencies:
confbox: 0.1.7
mlly: 1.7.1
pathe: 1.1.2
playwright-core@1.45.0: {}
playwright@1.45.0:
dependencies:
playwright-core: 1.45.0
optionalDependencies:
fsevents: 2.3.2
plist@3.1.0:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@xmldom/xmldom': 0.8.10
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
base64-js: 1.5.1
xmlbuilder: 15.1.1
pngjs@3.4.0: {}
portfinder@1.0.32:
dependencies:
async: 2.6.4
debug: 3.2.7
mkdirp: 0.5.6
transitivePeerDependencies:
- supports-color
possible-typed-array-names@1.0.0: {}
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
postcss-import@15.1.0(postcss@8.4.45):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
postcss: 8.4.45
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
postcss-value-parser: 4.2.0
read-cache: 1.0.0
resolve: 1.22.8
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
postcss-inline-svg@6.0.0(postcss@8.4.45):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
css-select: 5.1.0
dom-serializer: 2.0.0
htmlparser2: 8.0.2
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
postcss: 8.4.45
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
postcss-value-parser: 4.2.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
postcss-js@4.0.1(postcss@8.4.45):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
camelcase-css: 2.0.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
postcss: 8.4.45
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
postcss-load-config@4.0.2(postcss@8.4.45):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
lilconfig: 3.1.2
yaml: 2.4.5
optionalDependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
postcss: 8.4.45
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
postcss-nested@6.0.1(postcss@8.4.45):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
postcss: 8.4.45
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
postcss-selector-parser: 6.1.0
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
postcss-nesting@12.1.5(postcss@8.4.45):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@csstools/selector-resolve-nested': 1.1.0(postcss-selector-parser@6.1.0)
'@csstools/selector-specificity': 3.1.1(postcss-selector-parser@6.1.0)
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
postcss: 8.4.45
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
postcss-selector-parser: 6.1.0
postcss-selector-parser@6.1.0:
dependencies:
cssesc: 3.0.0
util-deprecate: 1.0.2
postcss-value-parser@4.2.0: {}
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
postcss@8.4.45:
dependencies:
nanoid: 3.3.7
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
source-map-js: 1.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prebuild-install@7.1.2:
dependencies:
detect-libc: 2.0.3
expand-template: 2.0.3
github-from-package: 0.0.0
minimist: 1.2.8
mkdirp-classic: 0.5.3
napi-build-utils: 1.0.2
node-abi: 3.65.0
pump: 3.0.0
rc: 1.2.8
simple-get: 4.0.1
tar-fs: 2.1.1
tunnel-agent: 0.6.0
prelude-ls@1.2.1: {}
prettier-linter-helpers@1.0.0:
dependencies:
fast-diff: 1.3.0
prettier-plugin-organize-imports@4.0.0(prettier@3.3.2)(typescript@5.5.3)(vue-tsc@2.0.24(typescript@5.5.3)):
dependencies:
prettier: 3.3.2
typescript: 5.5.3
optionalDependencies:
vue-tsc: 2.0.24(typescript@5.5.3)
Optimize asset table rendering (#11382) - Depends on: - #11380 - Some optimizations for re-rendering assets table: - Omit `visibilities` from `state` in favor of passing each `AssetRow`'s `visibility` directly to the row. This minimizes spurious `state` updates. - Pass `id` and `parentId` to `AssetRow` instead of the entire object. This ensures that re-fetches do not force a re-render of the `AssetRow` - we are no longer passing a reference to the object, so we are now comparing by string comparison (which is almost always stable). # Important Notes None
2024-10-31 13:36:10 +03:00
prettier-plugin-tailwindcss@0.5.14(@ianvs/prettier-plugin-sort-imports@4.3.0(prettier@3.3.2))(prettier-plugin-organize-imports@4.0.0(prettier@3.3.2)(typescript@5.5.3)(vue-tsc@2.0.24(typescript@5.5.3)))(prettier@3.3.2):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
prettier: 3.3.2
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@ianvs/prettier-plugin-sort-imports': 4.3.0(prettier@3.3.2)
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
prettier-plugin-organize-imports: 4.0.0(prettier@3.3.2)(typescript@5.5.3)(vue-tsc@2.0.24(typescript@5.5.3))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
prettier@3.3.2: {}
pretty-format@29.7.0:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jest/schemas': 29.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
ansi-styles: 5.2.0
react-is: 18.3.1
process-nextick-args@2.0.1: {}
process@0.11.10: {}
progress@2.0.3: {}
promise-retry@2.0.1:
dependencies:
err-code: 2.0.3
retry: 0.12.0
prop-types@15.8.1:
dependencies:
loose-envify: 1.4.0
object-assign: 4.1.1
react-is: 16.13.1
proto-list@1.2.4: {}
prr@1.0.1:
optional: true
psl@1.9.0: {}
pump@3.0.0:
dependencies:
end-of-stream: 1.4.4
once: 1.4.0
punycode@1.3.2: {}
punycode@1.4.1: {}
punycode@2.3.1: {}
pure-rand@6.1.0: {}
MFA (#10875) * Draft checkbox component * Fixes in Setup Page * Invite Users * Add usergroup setup after subscription * Fix comments * Refetch Interval + Feature Toggles * Fix lint * Address issues * Fix Dialog * Assign users to the user group * Use transitions to navigate between steps * Small fixes * Improve styling for scrollbars * Fix typescript * OTP input * Fix setup logic * Show Setup dialog only for admins * Add otp * OTP input * 2FA settings section * Small improvements * Fixes * Small fixes * Remove w-full * TOTP at login * Fixes in 2FA * Fixes in types * Fix totp * Merge fixes * Merge fixes x2 * Merge fixes x2 * Fix types * Fix types * Fix cancel button * Fix reset button * Fix types * Fix prettier * Fix prettier * Fix lint * Fix lint * Fix control * Address prettier * Fix MFA mock * Fix sign in message * Fix tests * Address CR * Fix types
2024-09-13 16:00:31 +03:00
qrcode.react@3.1.0(react@18.3.1):
dependencies:
react: 18.3.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
qs@6.11.0:
dependencies:
side-channel: 1.0.6
qs@6.12.1:
dependencies:
side-channel: 1.0.6
qs@6.5.3: {}
querystring@0.2.0: {}
querystringify@2.2.0: {}
queue-microtask@1.2.3: {}
quick-lru@5.1.1: {}
railroad-diagrams@1.0.0: {}
randexp@0.4.6:
dependencies:
discontinuous-range: 1.0.0
ret: 0.1.15
raw-body@2.5.2:
dependencies:
bytes: 3.1.2
http-errors: 2.0.0
iconv-lite: 0.4.24
unpipe: 1.0.0
rc@1.2.8:
dependencies:
deep-extend: 0.6.0
ini: 1.3.8
minimist: 1.2.8
strip-json-comments: 2.0.1
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react-aria-components@1.3.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/date': 3.5.5
'@internationalized/string': 3.2.3
'@react-aria/collections': 3.0.0-alpha.4(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/color': 3.0.0-rc.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/dnd': 3.7.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/menu': 3.15.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/toolbar': 3.0.0-beta.8(react@18.3.1)
'@react-aria/tree': 3.0.0-alpha.5(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-aria/virtualizer': 4.0.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-stately/color': 3.7.2(react@18.3.1)
'@react-stately/layout': 4.0.2(react@18.3.1)
'@react-stately/menu': 3.8.2(react@18.3.1)
'@react-stately/table': 3.12.2(react@18.3.1)
'@react-stately/utils': 3.10.4(react@18.3.1)
'@react-stately/virtualizer': 4.0.2(react@18.3.1)
'@react-types/color': 3.0.0-rc.1(react@18.3.1)
'@react-types/form': 3.7.6(react@18.3.1)
'@react-types/grid': 3.2.8(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
'@react-types/table': 3.10.1(react@18.3.1)
'@swc/helpers': 0.5.12
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
client-only: 0.0.1
react: 18.3.1
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react-aria: 3.34.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-dom: 18.3.1(react@18.3.1)
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react-stately: 3.32.2(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
use-sync-external-store: 1.2.2(react@18.3.1)
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react-aria@3.34.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@internationalized/string': 3.2.3
'@react-aria/breadcrumbs': 3.5.16(react@18.3.1)
'@react-aria/button': 3.9.8(react@18.3.1)
'@react-aria/calendar': 3.5.11(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/checkbox': 3.14.6(react@18.3.1)
'@react-aria/combobox': 3.10.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/datepicker': 3.11.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/dialog': 3.5.17(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/dnd': 3.7.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/focus': 3.18.2(react@18.3.1)
'@react-aria/gridlist': 3.9.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/i18n': 3.12.2(react@18.3.1)
'@react-aria/interactions': 3.22.3(react@18.3.1)
'@react-aria/label': 3.7.11(react@18.3.1)
'@react-aria/link': 3.7.4(react@18.3.1)
'@react-aria/listbox': 3.13.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/menu': 3.15.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/meter': 3.4.16(react@18.3.1)
'@react-aria/numberfield': 3.11.6(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/overlays': 3.23.2(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/progress': 3.4.16(react@18.3.1)
'@react-aria/radio': 3.10.7(react@18.3.1)
'@react-aria/searchfield': 3.7.8(react@18.3.1)
'@react-aria/select': 3.14.9(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/selection': 3.19.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/separator': 3.4.2(react@18.3.1)
'@react-aria/slider': 3.7.11(react@18.3.1)
'@react-aria/ssr': 3.9.6(react@18.3.1)
'@react-aria/switch': 3.6.7(react@18.3.1)
'@react-aria/table': 3.15.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/tabs': 3.9.5(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/tag': 3.4.5(react-dom@18.3.1(react@18.3.1))(react@18.3.1)
'@react-aria/textfield': 3.14.8(react@18.3.1)
'@react-aria/tooltip': 3.7.7(react@18.3.1)
'@react-aria/utils': 3.25.3(react@18.3.1)
'@react-aria/visually-hidden': 3.8.15(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Show docs on Dashboard (#11391) Closes: https://github.com/enso-org/cloud-v2/issues/1445 PR is more or less ready for feedback,CR, and QA. # Read before looking into: **Known issues:** - [x] Need to adjust timings for the animations (they're a bit out of sync). - [x] After the latest rebase, the side panel might expand while clicking on the sidebar toggle. - [ ] Images no longer display. 🤦 - [x] Need to restore the functionality around spotlighting a component Demo: https://github.com/user-attachments/assets/8cec9ec0-4753-482e-8637-f3857b4396a5
2024-11-15 15:12:55 +03:00
react-compiler-runtime@19.0.0-beta-6fc168f-20241025(react@18.3.1):
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
dependencies:
react: 18.3.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react-dom@18.3.1(react@18.3.1):
dependencies:
loose-envify: 1.4.0
react: 18.3.1
scheduler: 0.23.2
react-error-boundary@4.0.13(react@18.3.1):
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/runtime': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-hook-form@7.52.0(react@18.3.1):
dependencies:
react: 18.3.1
react-is@16.13.1: {}
react-is@18.3.1: {}
react-refresh@0.14.2: {}
react-router-dom@6.24.0(react-dom@18.3.1(react@18.3.1))(react@18.3.1):
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@remix-run/router': 1.17.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
react-router: 6.24.0(react@18.3.1)
react-router@6.24.0(react@18.3.1):
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@remix-run/router': 1.17.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
react-stately@3.32.2(react@18.3.1):
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@react-stately/calendar': 3.5.4(react@18.3.1)
'@react-stately/checkbox': 3.6.8(react@18.3.1)
'@react-stately/collections': 3.10.9(react@18.3.1)
'@react-stately/combobox': 3.9.2(react@18.3.1)
'@react-stately/data': 3.11.6(react@18.3.1)
'@react-stately/datepicker': 3.10.2(react@18.3.1)
'@react-stately/dnd': 3.4.2(react@18.3.1)
'@react-stately/form': 3.0.5(react@18.3.1)
'@react-stately/list': 3.10.8(react@18.3.1)
'@react-stately/menu': 3.8.2(react@18.3.1)
'@react-stately/numberfield': 3.9.6(react@18.3.1)
'@react-stately/overlays': 3.6.10(react@18.3.1)
'@react-stately/radio': 3.10.7(react@18.3.1)
'@react-stately/searchfield': 3.5.6(react@18.3.1)
'@react-stately/select': 3.6.7(react@18.3.1)
'@react-stately/selection': 3.16.2(react@18.3.1)
'@react-stately/slider': 3.5.7(react@18.3.1)
'@react-stately/table': 3.12.2(react@18.3.1)
'@react-stately/tabs': 3.6.9(react@18.3.1)
'@react-stately/toggle': 3.7.7(react@18.3.1)
'@react-stately/tooltip': 3.4.12(react@18.3.1)
'@react-stately/tree': 3.8.4(react@18.3.1)
'@react-types/shared': 3.25.0(react@18.3.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
react: 18.3.1
react-toastify@9.1.3(react-dom@18.3.1(react@18.3.1))(react@18.3.1):
dependencies:
clsx: 1.2.1
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
react@18.3.1:
dependencies:
loose-envify: 1.4.0
read-cache@1.0.0:
dependencies:
pify: 2.3.0
read-chunk@1.0.1: {}
read-config-file@6.3.2:
dependencies:
config-file-ts: 0.2.6
dotenv: 9.0.2
dotenv-expand: 5.1.0
js-yaml: 4.1.0
json5: 2.2.3
lazy-val: 1.0.5
read-pkg@3.0.0:
dependencies:
load-json-file: 4.0.0
normalize-package-data: 2.5.0
path-type: 3.0.0
readable-stream@2.3.8:
dependencies:
core-util-is: 1.0.3
inherits: 2.0.4
isarray: 1.0.0
process-nextick-args: 2.0.1
safe-buffer: 5.1.2
string_decoder: 1.1.1
util-deprecate: 1.0.2
readable-stream@3.6.2:
dependencies:
inherits: 2.0.4
string_decoder: 1.3.0
util-deprecate: 1.0.2
readdir-glob@1.1.3:
dependencies:
minimatch: 5.1.6
readdirp@3.6.0:
dependencies:
picomatch: 2.3.1
reflect.getprototypeof@1.0.6:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-errors: 1.3.0
get-intrinsic: 1.2.4
globalthis: 1.0.3
which-builtin-type: 1.1.3
regenerator-runtime@0.14.1: {}
regexp.prototype.flags@1.5.2:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-errors: 1.3.0
set-function-name: 2.0.2
Share tanstack QueryClient between dashboard and IDE (#10431) * Share tanstack QueryClient between dashboard and IDE Part of #10400. * Lint * Review: Use enso-common * Remove outdated README * Naming * Fix * Lint * enso-common CODEOWNERS: GUI+Dashboard * Review: Prepare for GUI to be run from cloud entry point * Lint * Lint * Fix e2e tests * Fix e2e tests in CI? * Clean CI build * Revert "Clean CI build" This reverts commit 73f2fb797219dafc12abb996cfc6cbcfb596c094. * Fix redundant dependency * Work around a vue-query bug * Lint * fmt
2024-07-09 18:01:10 +03:00
remove-accents@0.5.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
request@2.88.2:
dependencies:
aws-sign2: 0.7.0
aws4: 1.13.0
caseless: 0.12.0
combined-stream: 1.0.8
extend: 3.0.2
forever-agent: 0.6.1
form-data: 2.3.3
har-validator: 5.1.5
http-signature: 1.2.0
is-typedarray: 1.0.0
isstream: 0.1.2
json-stringify-safe: 5.0.1
mime-types: 2.1.35
oauth-sign: 0.9.0
performance-now: 2.1.0
qs: 6.5.3
safe-buffer: 5.2.1
tough-cookie: 2.5.0
tunnel-agent: 0.6.0
uuid: 3.4.0
require-directory@2.1.1: {}
require-from-string@2.0.2: {}
requires-port@1.0.0: {}
resize-img@1.1.2:
dependencies:
bmp-js: 0.0.1
file-type: 3.9.0
get-stream: 2.3.1
jimp: 0.2.28
jpeg-js: 0.1.2
parse-png: 1.1.2
resolve-alpn@1.2.1: {}
resolve-from@4.0.0: {}
resolve-pkg-maps@1.0.0: {}
resolve@1.22.8:
dependencies:
is-core-module: 2.13.1
path-parse: 1.0.7
supports-preserve-symlinks-flag: 1.0.0
resolve@2.0.0-next.5:
dependencies:
is-core-module: 2.13.1
path-parse: 1.0.7
supports-preserve-symlinks-flag: 1.0.0
responselike@2.0.1:
dependencies:
lowercase-keys: 2.0.0
ret@0.1.15: {}
retry@0.12.0: {}
reusify@1.0.4: {}
rfdc@1.4.1: {}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
rimraf@6.0.1:
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
glob: 11.0.0
package-json-from-dist: 1.0.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
roarr@2.15.4:
dependencies:
boolean: 3.2.0
detect-node: 2.1.0
globalthis: 1.0.3
json-stringify-safe: 5.0.1
semver-compare: 1.0.0
sprintf-js: 1.1.3
optional: true
robust-predicates@3.0.2: {}
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
rollup@4.24.0:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/estree': 1.0.6
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@rollup/rollup-android-arm-eabi': 4.24.0
'@rollup/rollup-android-arm64': 4.24.0
'@rollup/rollup-darwin-arm64': 4.24.0
'@rollup/rollup-darwin-x64': 4.24.0
'@rollup/rollup-linux-arm-gnueabihf': 4.24.0
'@rollup/rollup-linux-arm-musleabihf': 4.24.0
'@rollup/rollup-linux-arm64-gnu': 4.24.0
'@rollup/rollup-linux-arm64-musl': 4.24.0
'@rollup/rollup-linux-powerpc64le-gnu': 4.24.0
'@rollup/rollup-linux-riscv64-gnu': 4.24.0
'@rollup/rollup-linux-s390x-gnu': 4.24.0
'@rollup/rollup-linux-x64-gnu': 4.24.0
'@rollup/rollup-linux-x64-musl': 4.24.0
'@rollup/rollup-win32-arm64-msvc': 4.24.0
'@rollup/rollup-win32-ia32-msvc': 4.24.0
'@rollup/rollup-win32-x64-msvc': 4.24.0
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
fsevents: 2.3.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
rrweb-cssom@0.6.0: {}
rrweb-cssom@0.7.1: {}
run-applescript@7.0.0: {}
run-parallel@1.2.0:
dependencies:
queue-microtask: 1.2.3
rw@1.3.3: {}
sade@1.8.1:
dependencies:
mri: 1.2.0
safe-array-concat@1.1.2:
dependencies:
call-bind: 1.0.7
get-intrinsic: 1.2.4
has-symbols: 1.0.3
isarray: 2.0.5
safe-buffer@5.1.2: {}
safe-buffer@5.2.1: {}
safe-regex-test@1.0.3:
dependencies:
call-bind: 1.0.7
es-errors: 1.3.0
is-regex: 1.1.4
safer-buffer@2.1.2: {}
sanitize-filename@1.6.3:
dependencies:
truncate-utf8-bytes: 1.0.2
sax@1.4.1: {}
saxes@6.0.0:
dependencies:
xmlchars: 2.2.0
scheduler@0.23.2:
dependencies:
loose-envify: 1.4.0
section-matter@1.0.0:
dependencies:
extend-shallow: 2.0.1
kind-of: 6.0.3
seedrandom@2.4.4: {}
semver-compare@1.0.0:
optional: true
semver@5.7.2: {}
semver@6.3.1: {}
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver@7.6.3: {}
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sentence-case@3.0.4:
dependencies:
no-case: 3.0.4
tslib: 2.6.3
upper-case-first: 2.0.2
serialize-error@7.0.1:
dependencies:
type-fest: 0.13.1
optional: true
set-function-length@1.2.1:
dependencies:
define-data-property: 1.1.4
es-errors: 1.3.0
function-bind: 1.1.2
get-intrinsic: 1.2.4
gopd: 1.0.1
has-property-descriptors: 1.0.2
set-function-name@2.0.2:
dependencies:
define-data-property: 1.1.4
es-errors: 1.3.0
functions-have-names: 1.2.3
has-property-descriptors: 1.0.2
setprototypeof@1.2.0: {}
sharp@0.31.3:
dependencies:
color: 4.2.3
detect-libc: 2.0.3
node-addon-api: 5.1.0
prebuild-install: 7.1.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
simple-get: 4.0.1
tar-fs: 2.1.1
tunnel-agent: 0.6.0
shebang-command@1.2.0:
dependencies:
shebang-regex: 1.0.0
shebang-command@2.0.0:
dependencies:
shebang-regex: 3.0.0
shebang-regex@1.0.0: {}
shebang-regex@3.0.0: {}
shell-quote@1.8.1: {}
shiki-es@0.2.0: {}
shuffle-seed@1.1.6:
dependencies:
seedrandom: 2.4.4
side-channel@1.0.6:
dependencies:
call-bind: 1.0.7
es-errors: 1.3.0
get-intrinsic: 1.2.4
object-inspect: 1.13.1
siginfo@2.0.0: {}
signal-exit@4.1.0: {}
simple-concat@1.0.1: {}
simple-get@4.0.1:
dependencies:
decompress-response: 6.0.0
once: 1.4.0
simple-concat: 1.0.1
simple-swizzle@0.2.2:
dependencies:
is-arrayish: 0.3.2
simple-update-notifier@2.0.0:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sirv@2.0.4:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@polka/url': 1.0.0-next.25
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mrmime: 2.0.0
totalist: 3.0.1
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
sirv@3.0.0:
dependencies:
'@polka/url': 1.0.0-next.25
mrmime: 2.0.0
totalist: 3.0.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
slash@4.0.0: {}
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
slashes@3.0.12: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
slice-ansi@3.0.0:
dependencies:
ansi-styles: 4.3.0
astral-regex: 2.0.0
is-fullwidth-code-point: 3.0.0
optional: true
smart-buffer@4.2.0:
optional: true
snake-case@3.0.4:
dependencies:
dot-case: 3.0.4
tslib: 2.6.3
source-map-js@1.2.0: {}
source-map-support@0.5.21:
dependencies:
buffer-from: 1.1.2
source-map: 0.6.1
source-map@0.6.1: {}
spdx-correct@3.2.0:
dependencies:
spdx-expression-parse: 3.0.1
spdx-license-ids: 3.0.17
spdx-exceptions@2.5.0: {}
spdx-expression-parse@3.0.1:
dependencies:
spdx-exceptions: 2.5.0
spdx-license-ids: 3.0.17
spdx-expression-parse@4.0.0:
dependencies:
spdx-exceptions: 2.5.0
spdx-license-ids: 3.0.17
spdx-license-ids@3.0.17: {}
speakingurl@14.0.1: {}
spectorjs@0.9.30:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@shaderfrog/glsl-parser': 2.1.5
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sprintf-js@1.0.3: {}
sprintf-js@1.1.3:
optional: true
sql-formatter@13.1.0:
dependencies:
argparse: 2.0.1
get-stdin: 8.0.0
nearley: 2.20.1
sshpk@1.18.0:
dependencies:
asn1: 0.2.6
assert-plus: 1.0.0
bcrypt-pbkdf: 1.0.2
dashdash: 1.14.1
ecc-jsbn: 0.1.2
getpass: 0.1.7
jsbn: 0.1.1
safer-buffer: 2.1.2
tweetnacl: 0.14.5
stackback@0.0.2: {}
stat-mode@1.0.0: {}
state-local@1.0.7: {}
statuses@1.5.0: {}
statuses@2.0.1: {}
std-env@3.7.0: {}
stream-to-buffer@0.1.0:
dependencies:
stream-to: 0.2.2
stream-to@0.2.2: {}
strict-event-emitter-types@2.0.0: {}
string-length@5.0.1:
dependencies:
char-regex: 2.0.1
strip-ansi: 7.1.0
string-width@4.2.3:
dependencies:
emoji-regex: 8.0.0
is-fullwidth-code-point: 3.0.0
strip-ansi: 6.0.1
string-width@5.1.2:
dependencies:
eastasianwidth: 0.2.0
emoji-regex: 9.2.2
strip-ansi: 7.1.0
string.prototype.matchall@4.0.11:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-errors: 1.3.0
es-object-atoms: 1.0.0
get-intrinsic: 1.2.4
gopd: 1.0.1
has-symbols: 1.0.3
internal-slot: 1.0.7
regexp.prototype.flags: 1.5.2
set-function-name: 2.0.2
side-channel: 1.0.6
string.prototype.padend@3.1.6:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-object-atoms: 1.0.0
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
string.prototype.repeat@1.0.0:
dependencies:
define-properties: 1.2.1
es-abstract: 1.23.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
string.prototype.trim@1.2.9:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-abstract: 1.23.3
es-object-atoms: 1.0.0
string.prototype.trimend@1.0.8:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-object-atoms: 1.0.0
string.prototype.trimstart@1.0.8:
dependencies:
call-bind: 1.0.7
define-properties: 1.2.1
es-object-atoms: 1.0.0
string_decoder@1.1.1:
dependencies:
safe-buffer: 5.1.2
string_decoder@1.3.0:
dependencies:
safe-buffer: 5.2.1
strip-ansi@6.0.1:
dependencies:
ansi-regex: 5.0.1
strip-ansi@7.1.0:
dependencies:
ansi-regex: 6.0.1
strip-bom-string@1.0.0: {}
strip-bom@3.0.0: {}
strip-final-newline@3.0.0: {}
strip-json-comments@2.0.1: {}
strip-json-comments@3.1.1: {}
strip-literal@2.1.0:
dependencies:
js-tokens: 9.0.0
style-mod@4.1.2: {}
sucrase@3.35.0:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@jridgewell/gen-mapping': 0.3.5
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
commander: 4.1.1
glob: 10.4.2
lines-and-columns: 1.2.4
mz: 2.7.0
pirates: 4.0.6
ts-interface-checker: 0.1.13
sumchecker@3.0.1:
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
superjson@2.2.1:
dependencies:
copy-anything: 3.0.5
supports-color@5.5.0:
dependencies:
has-flag: 3.0.0
supports-color@7.2.0:
dependencies:
has-flag: 4.0.0
supports-preserve-symlinks-flag@1.0.0: {}
svg-tags@1.0.0: {}
symbol-tree@3.2.4: {}
New Signup flow (#10616)
2024-08-01 12:35:41 +03:00
synckit@0.9.1:
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@pkgr/core': 0.1.1
Inline modules in `app/ide-desktop/` (#10305) - Remove unnecessary modules - Remove `ts-plugin-namespace-auto-import` as it was a workaround to use the non-conventional `import *` convention - Remove `esbuild-plugin-copy-directories` as it is unuse - Inline modules that are only ever used once - Inline `project-manager-shim` into `gui2` - it is only used during `gui2`'s dev mode - Inline `content-config` into `client` - Flatten `app/ide-desktop/lib/` to `app/ide-desktop/` - Flatten `app/ide-desktop/lib/dashboard/` to `app/dashboard/` # Important Notes - As mentioned above, all remaining modules have been moved up from `app/ide-desktop/lib/` to `app/ide-desktop/`. It's not ideal but I'd rather hold off on moving them anywhere else before we have a consensus on what should go where. - (That is to say, this may not be the final directory structure - but I figure it's fine to get *something* done so that hopefully the rest of the restructuring is simpler.)
2024-07-17 12:10:42 +03:00
tslib: 2.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tailwind-merge@2.3.0:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/runtime': 7.24.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tailwind-variants@0.2.1(tailwindcss@3.4.4):
dependencies:
tailwind-merge: 2.3.0
tailwindcss: 3.4.4
tailwindcss-animate@1.0.7(tailwindcss@3.4.4):
dependencies:
tailwindcss: 3.4.4
tailwindcss-react-aria-components@1.1.3(tailwindcss@3.4.4):
dependencies:
tailwindcss: 3.4.4
tailwindcss@3.4.4:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@alloc/quick-lru': 5.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
arg: 5.0.2
chokidar: 3.6.0
didyoumean: 1.2.2
dlv: 1.1.3
fast-glob: 3.3.2
glob-parent: 6.0.2
is-glob: 4.0.3
jiti: 1.21.6
lilconfig: 2.1.0
micromatch: 4.0.5
normalize-path: 3.0.0
object-hash: 3.0.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
postcss: 8.4.45
postcss-import: 15.1.0(postcss@8.4.45)
postcss-js: 4.0.1(postcss@8.4.45)
postcss-load-config: 4.0.2(postcss@8.4.45)
postcss-nested: 6.0.1(postcss@8.4.45)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
postcss-selector-parser: 6.1.0
resolve: 1.22.8
sucrase: 3.35.0
transitivePeerDependencies:
- ts-node
tar-fs@2.1.1:
dependencies:
chownr: 1.1.4
mkdirp-classic: 0.5.3
pump: 3.0.0
tar-stream: 2.2.0
tar-stream@2.2.0:
dependencies:
bl: 4.1.0
end-of-stream: 1.4.4
fs-constants: 1.0.0
inherits: 2.0.4
readable-stream: 3.6.2
tar@6.2.1:
dependencies:
chownr: 2.0.0
fs-minipass: 2.1.0
minipass: 5.0.0
minizlib: 2.1.2
mkdirp: 1.0.4
yallist: 4.0.0
temp-file@3.4.0:
dependencies:
async-exit-hook: 2.0.1
fs-extra: 10.1.0
test-exclude@6.0.0:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@istanbuljs/schema': 0.1.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
glob: 7.2.3
minimatch: 3.1.2
text-table@0.2.0: {}
thenify-all@1.6.0:
dependencies:
thenify: 3.3.1
thenify@3.3.1:
dependencies:
any-promise: 1.3.0
tiny-invariant@1.3.3: {}
tinybench@2.8.0: {}
tinycolor2@1.6.0: {}
tinypool@0.8.4: {}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
tinyrainbow@1.2.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
tinyspy@2.2.1: {}
tmp-promise@3.0.3:
dependencies:
tmp: 0.2.3
tmp@0.2.3: {}
to-fast-properties@2.0.0: {}
to-ico@1.1.5:
dependencies:
arrify: 1.0.1
buffer-alloc: 1.2.0
image-size: 0.5.5
parse-png: 1.1.2
resize-img: 1.1.2
to-regex-range@5.0.1:
dependencies:
is-number: 7.0.0
toidentifier@1.0.1: {}
tosource@2.0.0-alpha.3: {}
totalist@3.0.1: {}
tough-cookie@2.5.0:
dependencies:
psl: 1.9.0
punycode: 2.3.1
tough-cookie@4.1.4:
dependencies:
psl: 1.9.0
punycode: 2.3.1
universalify: 0.2.0
url-parse: 1.5.10
tr46@0.0.3: {}
tr46@5.0.0:
dependencies:
punycode: 2.3.1
truncate-utf8-bytes@1.0.2:
dependencies:
utf8-byte-length: 1.0.5
ts-api-utils@1.3.0(typescript@5.5.3):
dependencies:
typescript: 5.5.3
ts-interface-checker@0.1.13: {}
ts-results@3.3.0: {}
tslib@2.6.3: {}
tsx@4.16.0:
dependencies:
esbuild: 0.21.5
get-tsconfig: 4.7.5
optionalDependencies:
fsevents: 2.3.3
tunnel-agent@0.6.0:
dependencies:
safe-buffer: 5.2.1
tweetnacl@0.14.5: {}
type-check@0.4.0:
dependencies:
prelude-ls: 1.2.1
type-detect@4.0.8: {}
type-fest@0.13.1:
optional: true
type-fest@0.20.2: {}
type-is@1.6.18:
dependencies:
media-typer: 0.3.0
mime-types: 2.1.35
typed-array-buffer@1.0.2:
dependencies:
call-bind: 1.0.7
es-errors: 1.3.0
is-typed-array: 1.1.13
typed-array-byte-length@1.0.1:
dependencies:
call-bind: 1.0.7
for-each: 0.3.3
gopd: 1.0.1
has-proto: 1.0.3
is-typed-array: 1.1.13
typed-array-byte-offset@1.0.2:
dependencies:
available-typed-arrays: 1.0.7
call-bind: 1.0.7
for-each: 0.3.3
gopd: 1.0.1
has-proto: 1.0.3
is-typed-array: 1.1.13
typed-array-length@1.0.6:
dependencies:
call-bind: 1.0.7
for-each: 0.3.3
gopd: 1.0.1
has-proto: 1.0.3
is-typed-array: 1.1.13
possible-typed-array-names: 1.0.0
Metadata should not depend on absolute text spans (#11390) close #11304 Changelog: - update: add `ide.snapshot` optional metadata field containing the source code of the file - update: `syncFileContents` method tries to repair the metadata spans when it detects that the source file was edited and the received code does not match the code stored in the `ide.snapshot` metadata field # Important Notes Tested in gui
2024-10-28 12:41:46 +03:00
typescript-eslint@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3):
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@typescript-eslint/eslint-plugin': 8.11.0(@typescript-eslint/parser@8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3))(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
'@typescript-eslint/parser': 8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
'@typescript-eslint/utils': 8.11.0(eslint@9.13.0(jiti@1.21.6))(typescript@5.5.3)
Unify Frontend App (#11287) Fixes #10668 Fixes #8484 Summary of changes: * `gui2` and `dashboard` are merged to `gui` directory. Various configs were merged (package.json, playwrigth, TS...). The src and e2e directories are split to `dashboard` and `project-view` for now. * E2E tests run two servers on different ports. The tests are organized in projects. This is also to be changed soon, as we plan to [use better mocking in GUI/ProjectView](#9726) * ESlint configs were merged to central `eslint.config.mjs`, and that file was moved to repository root. We kept the dashboard lints, but they can be relaxed. The dashboard code was changed to meet GUI lints. * Also, the versions of linter plugins were bumped, and code fixed. * The ide-desktop/client no longer has `dashboard` dependency - the only type used there was moved to common package. * `common` package moved to `app`.
2024-10-11 21:23:02 +03:00
optionalDependencies:
typescript: 5.5.3
transitivePeerDependencies:
- eslint
- supports-color
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
typescript@5.5.3: {}
uc.micro@1.0.6: {}
ufo@1.5.3: {}
unbox-primitive@1.0.2:
dependencies:
call-bind: 1.0.7
has-bigints: 1.0.2
has-symbols: 1.0.3
which-boxed-primitive: 1.0.2
undici-types@5.26.5: {}
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
undici-types@6.19.8: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
unfetch@4.2.0: {}
universal-cookie@4.0.4:
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/cookie': 0.3.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
cookie: 0.4.2
universalify@0.1.2: {}
universalify@0.2.0: {}
universalify@2.0.1: {}
unpipe@1.0.0: {}
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
upath@2.0.1: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
update-browserslist-db@1.1.0(browserslist@4.23.3):
dependencies:
browserslist: 4.23.3
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
escalade: 3.2.0
picocolors: 1.1.0
Dashboard UX improvements (#10868) - Fix dropdown focus issues - Keyboard navigation to/from dropdowns and between options - Mouse focus to/from dropdowns (there is no mouse navigation between options) - Use new inputs in "new secret" modal - Simplify form types - Switch activity log date filters to use `DatePicker` which is a wrapper around a `react-aria-components` input - Update `react-aria-components` - Prevent Navigator2D from handling event if it has already been `defaultPrevented` - Switch from `*` imports to `{}` imports for various files - Switch assets table row headings to use new components # Important Notes None
2024-08-29 08:54:21 +03:00
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
upper-case-first@2.0.2:
dependencies:
tslib: 2.6.3
upper-case@2.0.2:
dependencies:
tslib: 2.6.3
uri-js@4.4.1:
dependencies:
punycode: 2.3.1
url-parse@1.5.10:
dependencies:
querystringify: 2.2.0
requires-port: 1.0.0
url-regex@3.2.0:
dependencies:
ip-regex: 1.0.3
url@0.11.0:
dependencies:
punycode: 1.3.2
querystring: 0.2.0
url@0.11.3:
dependencies:
punycode: 1.4.1
qs: 6.12.1
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
use-sync-external-store@1.2.0(react@18.3.1):
dependencies:
react: 18.3.1
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
use-sync-external-store@1.2.2(react@18.3.1):
dependencies:
react: 18.3.1
utf8-byte-length@1.0.5: {}
util-deprecate@1.0.2: {}
utils-merge@1.0.1: {}
uuid@3.4.0: {}
validate-npm-package-license@3.0.4:
dependencies:
spdx-correct: 3.2.0
spdx-expression-parse: 3.0.1
validator@13.12.0: {}
vary@1.1.2: {}
veaury@2.4.1(react-dom@18.3.1(react@18.3.1))(react@18.3.1):
dependencies:
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
verror@1.10.0:
dependencies:
assert-plus: 1.0.0
core-util-is: 1.0.2
extsprintf: 1.4.1
verror@1.10.1:
dependencies:
assert-plus: 1.0.0
core-util-is: 1.0.2
extsprintf: 1.4.1
optional: true
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite-hot-client@0.2.3(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite-node@0.34.7(@types/node@22.9.0)(lightningcss@1.25.1):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
cac: 6.7.14
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
mlly: 1.7.1
pathe: 1.1.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@types/node'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- less
- lightningcss
- sass
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
- sass-embedded
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- stylus
- sugarss
- supports-color
- terser
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite-node@1.6.0(@types/node@22.9.0)(lightningcss@1.25.1):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
cac: 6.7.14
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pathe: 1.1.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@types/node'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- less
- lightningcss
- sass
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
- sass-embedded
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- stylus
- sugarss
- supports-color
- terser
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite-node@2.0.4(@types/node@22.9.0)(lightningcss@1.25.1):
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
dependencies:
cac: 6.7.14
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
pathe: 1.1.2
tinyrainbow: 1.2.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@types/node'
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
- less
- lightningcss
- sass
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
- sass-embedded
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
- stylus
- sugarss
- supports-color
- terser
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
vite-plugin-inspect@0.8.7(rollup@4.24.0)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@antfu/utils': 0.7.10
'@rollup/pluginutils': 5.1.0(rollup@4.24.0)
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
error-stack-parser-es: 0.1.5
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
fs-extra: 11.2.0
open: 10.1.0
perfect-debounce: 1.0.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
sirv: 2.0.4
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- rollup
- supports-color
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
vite-plugin-vue-devtools@7.6.3(rollup@4.24.0)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))(vue@3.5.2(typescript@5.5.3)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
'@vue/devtools-core': 7.6.3(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))(vue@3.5.2(typescript@5.5.3))
'@vue/devtools-kit': 7.6.3
'@vue/devtools-shared': 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
execa: 8.0.1
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
sirv: 3.0.0
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
vite-plugin-inspect: 0.8.7(rollup@4.24.0)(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
vite-plugin-vue-inspector: 5.2.0(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1))
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
- '@nuxt/kit'
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- rollup
- supports-color
- vue
Reconnect visualizations when switching their types (#11494) Fixes #11426 Now, visualizations should no longer receive stale data props cached from previous visualizations opened on the same node. We do so by changing the visualization ID (reattaching the visualization). This does not protect from unhandled exceptions happening inside visualizations, though, so a bigger fix will be provided separately. https://github.com/user-attachments/assets/821b3c11-818e-403b-812d-b3768399b3a4
2024-11-13 13:56:34 +03:00
vite-plugin-vue-inspector@5.2.0(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@babel/core': 7.25.2
'@babel/plugin-proposal-decorators': 7.24.7(@babel/core@7.25.2)
'@babel/plugin-syntax-import-attributes': 7.24.7(@babel/core@7.25.2)
'@babel/plugin-syntax-import-meta': 7.10.4(@babel/core@7.25.2)
'@babel/plugin-transform-typescript': 7.24.7(@babel/core@7.25.2)
'@vue/babel-plugin-jsx': 1.2.2(@babel/core@7.25.2)
'@vue/compiler-dom': 3.5.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
kolorist: 1.8.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
magic-string: 0.30.11
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite-plugin-wasm@3.3.0(vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)):
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
dependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite@5.4.10(@types/node@22.9.0)(lightningcss@1.25.1):
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
dependencies:
esbuild: 0.21.5
postcss: 8.4.45
rollup: 4.24.0
optionalDependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
fsevents: 2.3.3
lightningcss: 1.25.1
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vitest@1.6.0(@types/node@22.9.0)(jsdom@24.1.0)(lightningcss@1.25.1):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vitest/expect': 1.6.0
'@vitest/runner': 1.6.0
'@vitest/snapshot': 1.6.0
'@vitest/spy': 1.6.0
'@vitest/utils': 1.6.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
acorn-walk: 8.3.3
chai: 4.4.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
execa: 8.0.1
local-pkg: 0.5.0
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
magic-string: 0.30.11
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
pathe: 1.1.2
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
picocolors: 1.1.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
std-env: 3.7.0
strip-literal: 2.1.0
tinybench: 2.8.0
tinypool: 0.8.4
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
vite: 5.4.10(@types/node@22.9.0)(lightningcss@1.25.1)
vite-node: 1.6.0(@types/node@22.9.0)(lightningcss@1.25.1)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
why-is-node-running: 2.2.2
optionalDependencies:
Drop git dependency on enso-bot repository (#11539)
2024-11-12 21:25:19 +03:00
'@types/node': 22.9.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
jsdom: 24.1.0
transitivePeerDependencies:
- less
- lightningcss
- sass
Add React compiler (#11405) This PR adds React Compiler to the dashboard Read more about the compiler: https://github.com/reactwg/react-compiler/discussions/5 - This PR expects that these PRs are merged: - #11380 - #11382 ## Reasoning On our codebase adding React compiler led to significant perf improvements across the whole app. But the most impact was on the AssetsTable (see video attachment). Adding React compiler reduced the rerender scope of the AssetsTable from the whole table to the certain elements that changed, and made the table much more usable. Without compiler (page freezed): https://github.com/user-attachments/assets/16505b40-123b-4153-9c22-880f5dfa211c Compiler solves the issue: https://github.com/user-attachments/assets/6a298876-f28d-4b3d-8247-50b0c7ecb7f8 This PR requires thorough testing of the dashboard for potential bugs introduced by the compiler
2024-10-31 15:10:22 +03:00
- sass-embedded
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
- stylus
- sugarss
- supports-color
- terser
vscode-uri@3.0.8: {}
Table Editor Widget (#10774) Fixes #10293 The Table Editor Widget allows adding rows and columns, editing cells and renaming columns. [Screencast from 2024-08-07 13-17-37.webm](https://github.com/user-attachments/assets/d2e708b5-6516-4107-bc17-f018e455c111) # Important Notes * The parts of Table Visualization which were useful for the widget were put in vue component. On this occasion, we use aggrid vue.
2024-08-12 17:45:58 +03:00
vue-component-type-helpers@2.0.29: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue-demi@0.14.10(vue@3.5.2(typescript@5.5.3)):
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
dependencies:
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
Local Dashboard fixes (#10958) - Fix most of https://github.com/enso-org/cloud-v2/issues/1459 - Prevent click + click from triggering rename on Windows and Linux. Behavior is preserved on macOS. - Fix text in Drive when root folder is empty - Properly remove the "Drop here to upload box" after a file is dropped - "Copy as path" now unconditionally uses `/` for path delimiters, even on Windows - Duplicating a project in the root folder on Windows no longer errors - Extra folders in the sidebar now (correctly) show folder name, rather than path, on Windows - Mouse pointer when dragging to a folder is now move, not copy Not addressed: - [no-repro] Tooltips should have some latency before showing up - This should already be the case, although it may work weirdly (once the tooltip opens, there is no delay on subsequent tooltips opening until the last tooltip closes.) - [no-repro] Ctrl-click should add to selection - Column width should be resizable - This requires a refactor and therefore is considered out of scope for this PR - [no-repro] Choosing root folder needs a file browser - [no-repro] Choosing root folder doesn't do anything get the same list as we had before - [no-repro] Open in explorer didn't work in a file but did on project - possibly fixed by path changes. - [no-repro] Opening an enso-project by double clicking resulted on it being renamed with a (2) Related changes: - Make "root directory" picker's file browser default to the current root directory # Important Notes None
2024-09-08 09:54:41 +03:00
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
vue-eslint-parser@9.4.3(eslint@9.13.0(jiti@1.21.6)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
debug: 4.3.7
A set of little improvements. (#11386) 1. Bumped eslint and its plugins versions, and autofix new errors (mostly eslint disables which were no longer neccessary) 2. ~~Replace eslint with eslint-p which speed up linter a bit (at least on my machine)~~ - CI machines don't like it. 3. Fixed/worked around one problem with flacky selection _unit_ tests.
2024-10-24 10:38:08 +03:00
eslint: 9.13.0(jiti@1.21.6)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
eslint-scope: 7.2.2
eslint-visitor-keys: 3.4.3
espree: 9.6.1
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
esquery: 1.6.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
lodash: 4.17.21
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
transitivePeerDependencies:
- supports-color
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue-react-wrapper@0.3.1(vue@3.5.2(typescript@5.5.3)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/prop-types': 15.7.12
'@types/react': 18.3.3
'@types/react-dom': 18.0.3
'@types/scheduler': 0.23.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
csstype: 3.1.3
react: 18.3.1
react-dom: 18.3.1(react@18.3.1)
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue-resize@2.0.0-alpha.1(vue@3.5.2(typescript@5.5.3)):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue: 3.5.2(typescript@5.5.3)
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
vue-template-compiler@2.7.16:
dependencies:
de-indent: 1.0.2
he: 1.2.0
vue-tsc@2.0.24(typescript@5.5.3):
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@volar/typescript': 2.4.0-alpha.12
'@vue/language-core': 2.0.24(typescript@5.5.3)
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
semver: 7.6.3
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
typescript: 5.5.3
Update Vue (#11016) See: https://blog.vuejs.org/posts/vue-3-5
2024-09-10 20:18:35 +03:00
vue@3.5.2(typescript@5.5.3):
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
dependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@vue/compiler-dom': 3.5.2
'@vue/compiler-sfc': 3.5.2
'@vue/runtime-dom': 3.5.2
'@vue/server-renderer': 3.5.2(vue@3.5.2(typescript@5.5.3))
'@vue/shared': 3.5.2
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
optionalDependencies:
typescript: 5.5.3
w3c-keyname@2.2.8: {}
w3c-xmlserializer@5.0.0:
dependencies:
xml-name-validator: 5.0.0
webidl-conversions@3.0.1: {}
webidl-conversions@7.0.0: {}
whatwg-encoding@3.1.1:
dependencies:
iconv-lite: 0.6.3
whatwg-fetch@3.6.20: {}
whatwg-mimetype@4.0.0: {}
whatwg-url@14.0.0:
dependencies:
tr46: 5.0.0
webidl-conversions: 7.0.0
whatwg-url@5.0.0:
dependencies:
tr46: 0.0.3
webidl-conversions: 3.0.1
which-boxed-primitive@1.0.2:
dependencies:
is-bigint: 1.0.4
is-boolean-object: 1.1.2
is-number-object: 1.0.7
is-string: 1.0.7
is-symbol: 1.0.4
which-builtin-type@1.1.3:
dependencies:
function.prototype.name: 1.1.6
has-tostringtag: 1.0.2
is-async-function: 2.0.0
is-date-object: 1.0.5
is-finalizationregistry: 1.0.2
is-generator-function: 1.0.10
is-regex: 1.1.4
is-weakref: 1.0.2
isarray: 2.0.5
which-boxed-primitive: 1.0.2
which-collection: 1.0.2
which-typed-array: 1.1.15
which-collection@1.0.2:
dependencies:
is-map: 2.0.3
is-set: 2.0.3
is-weakmap: 2.0.2
is-weakset: 2.0.3
which-typed-array@1.1.15:
dependencies:
available-typed-arrays: 1.0.7
call-bind: 1.0.7
for-each: 0.3.3
gopd: 1.0.1
has-tostringtag: 1.0.2
which@1.3.1:
dependencies:
isexe: 2.0.0
which@2.0.2:
dependencies:
isexe: 2.0.0
why-is-node-running@2.2.2:
dependencies:
siginfo: 2.0.0
stackback: 0.0.2
word-wrap@1.2.5: {}
wrap-ansi@7.0.0:
dependencies:
ansi-styles: 4.3.0
string-width: 4.2.3
strip-ansi: 6.0.1
wrap-ansi@8.1.0:
dependencies:
ansi-styles: 6.2.1
string-width: 5.1.2
strip-ansi: 7.1.0
wrappy@1.0.2: {}
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws@8.18.0: {}
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
xhr@2.6.0:
dependencies:
global: 4.4.0
is-function: 1.0.2
parse-headers: 2.0.5
xtend: 4.0.2
xml-name-validator@4.0.0: {}
xml-name-validator@5.0.0: {}
xml-parse-from-string@1.0.1: {}
xml2js@0.5.0:
dependencies:
sax: 1.4.1
xmlbuilder: 11.0.1
xmlbuilder@11.0.1: {}
xmlbuilder@15.1.1: {}
xmlchars@2.2.0: {}
xtend@4.0.2: {}
y-leveldb@0.1.2(yjs@13.6.18):
dependencies:
level: 6.0.1
lib0: 0.2.94
yjs: 13.6.18
optional: true
y-protocols@1.0.6(yjs@13.6.18):
dependencies:
lib0: 0.2.94
yjs: 13.6.18
y-textarea@1.0.1(yjs@13.6.18):
dependencies:
yjs: 13.6.18
y-websocket@1.5.4(yjs@13.6.18):
dependencies:
lib0: 0.2.94
lodash.debounce: 4.0.8
y-protocols: 1.0.6(yjs@13.6.18)
yjs: 13.6.18
optionalDependencies:
Split ydoc server into separate module (#10735) # Important Notes The command to run the gui dev environment has been changed. Invoking the old command will print a message about that. From now on, use `pnpm dev:gui2` in repository root.
2024-08-08 15:12:05 +03:00
ws: 8.18.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
y-leveldb: 0.1.2(yjs@13.6.18)
transitivePeerDependencies:
- bufferutil
- utf-8-validate
y18n@5.0.8: {}
yallist@3.1.1: {}
yallist@4.0.0: {}
yaml@2.4.5: {}
yargs-parser@21.1.1: {}
yargs@17.6.2:
dependencies:
cliui: 8.0.1
Add support for touch-based graph navigation and selection (#11056) Fixes #9493 Tested on windows desktop (standard mouse), macbook touchpad and iphone, which should behave similarily to windows touchscreen devices.
2024-09-20 19:31:45 +03:00
escalade: 3.2.0
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
get-caller-file: 2.0.5
require-directory: 2.1.1
string-width: 4.2.3
y18n: 5.0.8
yargs-parser: 21.1.1
yauzl@2.10.0:
dependencies:
buffer-crc32: 0.2.13
fd-slicer: 1.1.0
yjs@13.6.18:
dependencies:
lib0: 0.2.94
yocto-queue@0.1.0: {}
yocto-queue@1.1.1: {}
zen-observable-ts@0.8.19:
dependencies:
tslib: 2.6.3
zen-observable: 0.8.15
zen-observable@0.8.15: {}
zip-stream@4.1.1:
dependencies:
archiver-utils: 3.0.4
compress-commons: 4.1.2
readable-stream: 3.6.2
Add eslint-react-compiler (#11404) * Add React compiler eslint rules and fix issues across reusable components * Fix compiler errors * Remove fail-on-warnings for eslint * Set max-warnings to 41 to match the amount of warnings introduced by react-compiler * Add comment for lint task
2024-10-28 15:58:41 +03:00
zod-validation-error@3.4.0(zod@3.23.8):
dependencies:
zod: 3.23.8
Migrate to pnpm (#10422) Fixes #10197 # Important Notes From now on, package installation will be using `pnpm install`. Installing it globally is fine for convenience, but it can also be used as `corepack pnpm install` without having to install anything other than node. For now, all other scripts are still invoked using `npm`, so we can still invoke them with usual `--workspace` setting. As far as I can tell that doesn't really have any other side effects and is identical as running the script through `pnpm run` in respective workspace project subdirectory.
2024-07-05 14:13:04 +03:00
zod@3.23.8: {}
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
zustand@4.5.4(@types/react@18.3.3)(react@18.3.1):
dependencies:
use-sync-external-store: 1.2.0(react@18.3.1)
optionalDependencies:
Restore pnpm-lock (#11514) Bypassing issue with CI
2024-11-12 13:05:07 +03:00
'@types/react': 18.3.3
Optimize assets table (#10522) - Fix https://github.com/enso-org/cloud-v2/issues/1379 - Stop re-rendering the entire `AssetsTable` on every `AssetEvent` - This is achieved by using `zustand` for fine-grained reactivity. Other misc fixes: - Fix "unique key prop" error in sidebar - Vertically center asset panel toggle icon in top bar - Limit width of asset names (show tooltip when asset name is too wide) # Important Notes None
2024-07-15 13:06:15 +03:00
react: 18.3.1
Reference in New Issue Copy Permalink