Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

npm WARN deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs #3412

Open
sergeylukin opened this issue Apr 14, 2024 · 1 comment

Comments

@sergeylukin
Copy link

  • NPM version (npm -v): 10.2.3
  • Node version (node -v): 20.10.0
  • Node Process (node -p process.versions):
    {
      node: '20.10.0',
      acorn: '8.10.0',
      ada: '2.7.2',
      ares: '1.20.1',
      base64: '0.5.0',
      brotli: '1.0.9',
      cjs_module_lexer: '1.2.2',
      cldr: '43.1',
      icu: '73.2',
      llhttp: '8.1.1',
      modules: '115',
      napi: '9',
      nghttp2: '1.57.0',
      nghttp3: '0.7.0',
      ngtcp2: '0.8.1',
      openssl: '3.0.12+quic',
      simdutf: '3.2.18',
      tz: '2023c',
      undici: '5.26.4',
      unicode: '15.0',
      uv: '1.46.0',
      uvwasi: '0.0.19',
      v8: '11.3.244.8-node.25',
      zlib: '1.2.13.1-motley'
    }
    
  • Node Platform (node -p process.platform): darwin
  • Node architecture (node -p process.arch): arm64
  • node-sass version (node -p "require('node-sass').info"):
    node-sass       9.0.0   (Wrapper)       [JavaScript]
    libsass         3.5.5   (Sass Compiler) [C/C++]
    
  • npm node-sass versions (npm ls node-sass):
    rms-client@1.1.35 /Users/sergey/code/work/rms-client
    └── node-sass@9.0.0
    

Screenshot 2024-04-14 at 16 19 09

Receiving:

npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm WARN deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs

when checking which dependency is using @npmcli/move-file getting following:

Screenshot 2024-04-14 at 16 19 52

@maltempi
Copy link

maltempi commented Apr 17, 2024

I believe this PR would fix it: #3395

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants