Skip to content

[3.0.2 or later] source-map-loader has deprecated methods. #225

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

Closed
stein2nd opened this issue Nov 27, 2023 · 1 comment · Fixed by #228
Closed

[3.0.2 or later] source-map-loader has deprecated methods. #225

stein2nd opened this issue Nov 27, 2023 · 1 comment · Fixed by #228

Comments

@stein2nd
Copy link

Bug report

npm WARN deprecated [email protected]: Use your platform's native atob() and btoa() methods instead

Actual Behavior

abab@2 0 6 deduped

Expected Behavior

How Do We Reproduce?

  1. Delete the "node_modules" folder and "package-lock.json".
  2. Execute "ncu", "ncu -u", "npm install --force" in order.

Please paste the results of npx webpack-cli info here, and mention other relevant information

System:

  • OS: macOS 14.1.1
  • CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
  • Memory: 1.26 GB / 32.00 GB
  • Shell: 3.2.57 - /bin/bash

Binaries:

  • Node: 21.2.0 - ~/.nodebrew/current/bin/node
  • Yarn: 1.22.21 - /usr/local/bin/yarn
  • npm: 10.2.4 - ~/.nodebrew/current/bin/npm

npmPackages:

  • @webpack-cli/generators: ^3.0.7 => 3.0.7
  • babel-loader: ^9.1.3 => 9.1.3
  • clean-webpack-plugin: ^4.0.0 => 4.0.0
  • copy-webpack-plugin: ^11.0.0 => 11.0.0
  • css-loader: ^6.8.1 => 6.8.1
  • css-minimizer-webpack-plugin: ^5.0.1 => 5.0.1
  • eslint-webpack-plugin: ^4.0.1 => 4.0.1
  • postcss-loader: ^7.3.3 => 7.3.3
  • sass-loader: ^13.3.2 => 13.3.2
  • source-map-loader: ^4.0.1 => 4.0.1
  • style-loader: ^3.3.3 => 3.3.3
  • stylelint-webpack-plugin: ^4.1.1 => 4.1.1
  • terser-webpack-plugin: ^5.3.9 => 5.3.9
  • ts-loader: ^9.5.1 => 9.5.1
  • webpack: ^5.89.0 => 5.89.0
  • webpack-bundle-analyzer: ^4.10.1 => 4.10.1
  • webpack-cli: ^5.1.4 => 5.1.4
@mbostwick mbostwick mentioned this issue Dec 3, 2023
5 tasks
@mbostwick
Copy link

There are a couple of packages there that will still give that warning, However, I routed a PR to fix this locally. It would involved having atleast node 16. I just bumped the minor version though since version 16 is out of support, so supported node versions should be fine..

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

Successfully merging a pull request may close this issue.

2 participants