v8.6.0

Compare Source

Minor Changes

• Some settings influence the structure of the lockfile, so we cannot reuse the lockfile if those settings change. As a result, we need to store such settings in the lockfile. This way we will know with which settings the lockfile has been created.

  A new field will now be present in the lockfile: settings. It will store the values of two settings: autoInstallPeers and excludeLinksFromLockfile. If someone tries to perform a frozen-lockfile installation and their active settings don't match the ones in the lockfile, then an error message will be thrown.

  The lockfile format version is bumped from v6.0 to v6.1.

  Related PR: #​6557
  Related issue: #​6312

• A new setting, exclude-links-from-lockfile, is now supported. When enabled, specifiers of local linked dependencies won't be duplicated in the lockfile.

  This setting was primarily added for use by Bit CLI, which links core aspects to node_modules from external directories. As such, the locations may vary across different machines, resulting in the generation of lockfiles with differing locations.

Patch Changes

• Don't print "Lockfile is up-to-date" message before finishing all the lockfile checks #​6544.
• When updating dependencies, preserve the range prefix in aliased dependencies. So npm:foo@1.0.0 becomes npm:foo@1.1.0.
• Print a meaningful error when a project referenced by the workspace: protocol is not found in the workspace #​4477.
• pnpm rebuild should not fail when node-linker is set to hoisted and there are skipped optional dependencies #​6553.
• Peers resolution should not fail when a linked in dependency resolves a peer dependency.
• Build projects in a workspace in correct order #​6568.

Our Gold Sponsors

Our Silver Sponsors

v4.3.9

Compare Source

• fix: fs.deny with leading double slash (#​13348) (813ddd6), closes #​13348
• fix: optimizeDeps during build and external ids (#​13274) (e3db771), closes #​13274
• fix(css): return deps if have no postcss plugins (#​13344) (28923fb), closes #​13344
• fix(legacy): style insert order (#​13266) (e444375), closes #​13266
• chore: revert prev release commit (2a30a07)
• release: v4.3.9 (5c9abf7)
• docs: optimizeDeps.needsInterop (#​13323) (b34e79c), closes #​13323
• test: respect commonjs options in playgrounds (#​13273) (19e8c68), closes #​13273
• refactor: simplify SSR options' if statement (#​13254) (8013a66), closes #​13254
• perf(ssr): calculate stacktrace offset lazily (#​13256) (906c4c1), closes #​13256

v2.3.1

Compare Source

• Drop npm from package.json "engines" config (#​476)

v2.3.0

Compare Source

This release corresponds with the release of yaml-types v0.2.0, an expanding library of custom tags or types for use with yaml.

This release contains no changes from v2.3.0-5, and the notes below include all changes from the v2.3.0-x prereleases.

Custom Tag Improvements

• Add export of createNode() & createPair() to 'yaml/util' (#​457)
• Add static from() methods to simplify tag development, and otherwise make extending custom collections easier (#​467)

TypeScript Improvements

• Add a second optional generic type argument Strict to Document instances. (#​441)
• Add types exports for TypeScript (#​463)
• Export StringifyContext type from 'yaml/util' (#​464)

Other New Features

• Add a toJS(doc, options?) method to nodes (#​451, #​458)
• Set explicit tag during createNode() for non-default tags (#​464)

Bugfixes

• Use correct argument order when stringifying flow collection comments (#​443)
• Improve first-line folding for block scalars (#​422)