* chore: dependencies maintenance
- upgrade node-fetch to latest stable version
- upgrade lru-cache and remove @types/lru-cache stub type definitions
- remove eslint disables in npm-resolver index.ts
- upgrade @types/validate-npm-package-name to v4 to match package major version
- upgrade dependencies in @pnpm/get-release-text
* updated pnpm.overrides section
* include changeset
* - update local.d.ts
- replace deprecated lru-cache maxAge option with ttl
* turn down node-fetch version to 3.0.0-beta.9 again since newer ones are ESM-only
* update changeset
* fix: read package manifest when verifyStoreIntegrity is false
* fixup: add test
* fixup: resolve manifest even if no package.json was found
* fixup: relocate function to read manifest from store
* fixup: add changeset
* fix(lockfile): change sorting of keys in lockfile
Make it more deterministic and prevent unnecessary churn in the lockfile.
It is useful when looking for affected projects after changes to the lockfile.
When the changes happen among various developers using various locale,
the locale specific sorting causes changes in the lockfile for extraneous projects.
Therefore, it could cause running unnecessary CI jobs, builds, releases and other
work that would not be needed otherwise.
* chore: add comment
Co-authored-by: Zoltan Kochan <z@kochan.io>
* chore: upgrade various dependencies
- upgrade syncpack from v6 to v8
- set syncpack workspace option to false to avoid changing workspace:* to exact version
* - remove deprecated @types/json5
- upgrade eslint-config-standard-with-typescript to v22
- install eslint-plugin-n which is now a required peer dependency
- upgrade eslint-plugin-promise to v6
- bump minimum node version to >=12.22.0 in @pnpm/eslint-config
* sync various @types/* packages to be at the same major version as the dep they provide types for
* fix new reported lint issues
* add changeset
* docs: update changesets
Co-authored-by: Zoltan Kochan <z@kochan.io>
* fix: don't include specifiers field in new experimental lockfile format
* test(lockfile-file): update arguments in normalizeLockfile test
* test: lockfile-file
Co-authored-by: Brandon Cheng <gluxon@users.noreply.github.com>
* fix: plugin-commands-deploy use path resolve on deploy target directory (#4980)
Previously the deploy target directory was specified as a relative path
to the workspace project root. This meant that absolute paths could not be used.
Now this uses the current working directory and allows absolute paths,
this is more in line with users expectations of unix command behaivour.
close#4980
* fix: allow both absolute and relative
* docs: update changesets
Co-authored-by: Zoltan Kochan <z@kochan.io>
