You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug github:feross/buffer version is not pinned and updates on every occasion (causes undesired pnpm-lock.yaml update on unrelated operations).
Expected behavior buffer is pinned to some specific github commit (or simply to ^6.0.3), not latest, and doesn't cause unrequested lockfile updates. This also prevents from sudden crashes due to breaking changes in buffer.
Environment:
OS: macOS
Node: 20.11.1
pnpm: 8.15.2
Additional context
To be honest I don't see why it's necessary to pull buffer from github and not from npm. Granted, it hasn't been published for 3 years, but at least simple operations (genEncryptedMasterKey, encrypt, decrypt) work fine with buffer@6.0.3.
The text was updated successfully, but these errors were encountered:
Describe the bug
github:feross/buffer
version is not pinned and updates on every occasion (causes undesiredpnpm-lock.yaml
update on unrelated operations).See:
easy-web-crypto/package.json
Line 42 in 0660046
To Reproduce
Steps to reproduce the behavior:
pnpm add easy-web-crypto
.pnpm-lock.yaml
to some older github.com/feross/buffer commit:pnpm add dotenv-cli
Expected behavior
buffer
is pinned to some specific github commit (or simply to ^6.0.3), notlatest
, and doesn't cause unrequested lockfile updates. This also prevents from sudden crashes due to breaking changes inbuffer
.Environment:
Additional context
To be honest I don't see why it's necessary to pull
buffer
from github and not from npm. Granted, it hasn't been published for 3 years, but at least simple operations (genEncryptedMasterKey
,encrypt
,decrypt
) work fine withbuffer@6.0.3
.The text was updated successfully, but these errors were encountered: