Nyazuki

In fact, found that the build did complete, it looks like it is an error message inside of a WARNING... which is kinda weird... I still think this is a...

> @Nyazuki what's your CRA or NextJS version? I dont use CRA or NextJS, the project ejected with customized configs, but it is running on node 14.18.1 webpack ^5.19.0 react...

Tried adding: resolve: { fallback: { crypto: false } } to webpack config will mute the warning/error, but not sure why and how did it work.

> I update the version with this config in `webpack`. Try the version `2.2.6` Same result with 2.2.6... still showing that warning

@lopesboa thanks for the tip. Unfortunately, due to other lib we are using(e.g. aws-amplify etc.) downgrade is not an option for us... I will just do the fallback trick on...

After 7.5 months and now working on another upgrade for my project dependencies, the issue still exist with new settings as follows: node: v16.15.1 "webpack": "^5.73.0" "encrypt-storage": "^2.2.10" "ts-loader": "^9.3.1",...

https://github.com/nondanee/UnblockNeteaseMusic/issues/709#issuecomment-794659395 试试看？同海外。

换了新电脑new setup后也遇到了这样的问题，不过刚刚试了去掉 -s 严格模式就可以用了。 但不清楚这个enable proxy limitation是什么用途。