未找到模块: 错误: 无法解析“加密”

小开

I ran into a similar issue lately while trying to use another library (tiff.js) in a small project I was experimenting with.

The way I got around this was to add the following to my package.json file, right after the devDependencies section.

"devDependencies": {
...
},
"browser": {
"crypto": false
}

This didn't seem to have any adverse effect when trying to use the library in the application.

小开

aws-sign2 is a NodeJS package (and crypto is a NodeJS module), but it looks like you're dealing with a web application. It makes sense that the crypto module is not available in that environment.

Would it be possible to complete what you need to do server-side? Otherwise, you may need to look for another package.

小开

I like R. Richards's answer, but I thought it would be useful to provide some more information.

This is a known issue with Angular, and the Angular CLI dev team seems to think it's a feature rather than a bug. I, as well as other developers in this issue thread, disagree. Contributors to that thread provided several workaround fixes, but my project didn't compile successfully until I implemented R. Richards' solution. I didn't revert the previous changes, though, so tacnoman's and GrandSchtroumpf's fixes may be of use to others.

Some, like clovis1122 here and others in that issue thread, have questioned why a web app would need access to these libraries and why the necessary tasks can't be completed on the server side instead. I can't speak for everyone, but my use case is that, when authenticating a user account, Strapi responds with a JSON Web Token string that must be decoded by the client. Since the necessary library depends on crypto and stream, you won't be able to extract the JWT expiration time unless those dependencies are available.

In case anyone has trouble extrapolating from R. Richards' answer, you'll have to set to false any dependencies that are showing up in "can't resolve x" errors. For example, the critical part of my package.json is:

    "browser": {
"crypto": false,
"stream": false
}

小开

Adding this setting in tsconfig.json file under that project resolve this warning

"compilerOptions": {
"baseUrl": "./",
"paths": {
"crypto": [
"node_modules/crypto-js"
]
}

小开

After a deep a research i found that the solution is very simple: replace import * as CryptoJS from 'crypto-js'; with declare var CryptoJS;

小开

I thought I would expand on what Tarique Ahmed wrote in his answer.

I was using an npm module that had the following line in the code:

const crypto = require('crypto');

I couldn't add:

"browser": {
"crypto": false
}

to the package.json because the crypto package had to be part of the build.

It turns out that during the compilation process Angular seems to have decided to install the crypto-browserify package instead of crypto.

Adding the following to the tsconfig.json file instructs the build to use the crypto-browserify library every time that crypto is required. As you can see, I had the same issue for the stream package.

"paths": {
"crypto": [
"node_modules/crypto-browserify"
],
"stream": [
"node_modules/stream-browserify"
]
}

小开

After having the same issue with Angular 11 and crypto-js 4 (and manually setting the path in tsconfig.json), I found rolling back crypto-js to version 3.1.9-1 fixed the issue. It seems a change made in version 4 caused the issue.

npm install crypto-js@3.1.9-1

Explained here in repo issues:

GitHub issue

小开

Using direct import may not work with ES6 Enviornment..

This may help you.

$ npm i crypto-js@latest // For using latest version 4

import AES from 'crypto-js/aes';
import Utf8 from 'crypto-js/enc-utf8';
import { secretKey } from './environments/environment';


/** Encryption */
const data = {key: 'Test Value'};
const ciphertext = AES.encrypt(JSON.stringify(data), secretKey).toString();
console.log('Encrypted Data', ciphertext);


/** Decryption */
const bytes = AES.decrypt(ciphertext, secretKey);
const decryptedData = JSON.parse(bytes.toString(Utf8));
console.log('Decrypted Data', decryptedData);

https://github.com/brix/crypto-js/issues/168#issuecomment-785617218

小开

Add the option allowedCommonJsDependencies with literal "crypto-js" in a array, this in file angular.json:

"architect":
"build": {
"options": {
"allowedCommonJsDependencies": [
"crypto-js"
]
},
}
}

This will disable all warnings, tested in Angular 11.

小开

If you upgraded to Webpack 5, you need to add this to your webpack config file:

resolve: {
fallback: { crypto: false },
},

小开

For Laravel Inertia JS project, my solution was:

1- Add dependencies to package.json

   "dependencies": {
"crypto-browserify": "3.12.0",
"crypto-random-string": "^3.3.0",
"stream": "^0.0.2"
}

2-In webpack.config.js:

const path = require('path');


module.exports = {
resolve: {
alias: {
'@': path.resolve('resources/js'),
},
fallback: {
crypto: require.resolve('crypto-browserify'),
stream: require.resolve('stream'),
},
},
};

3-Install, build and run:

npm install && npm run watch

小开

My problem was that I was trying to build to node and web using the same code, but is not possible to built to web while importing a WebSocket dependency, ws in my case

So the solution is by using a wrapper:

Install a wrapper, I will use isomorphic-ws because is made for ws

npm i --save isomorphic-ws

Remove const WebSocket = require('ws')

Replace with:

const WebSocket = require('isomorphic-ws')

小开

I have resolved my issue using below steps:

Add below to tsconfig.json to resolve crypto warning:

"paths": {
"crypto": [
"node_modules/crypto-js"
]
},

and add below to angular.json

"options": {
"allowedCommonJsDependencies": [
"crypto-js"
],
...
}

小开

I had this problem in ReactJS with create-react-app(facebook)

Solution:

First install the necessary packages "crypto-browserify"
Modify webpack.config.js in reactjs with create-react-app this file is inside:

node_modules/react-scripts/config/webpack.config.js

Search module.exports and inside this function there is a return:

module.exports = function (webpackEnv) {
...
return {
...
resolve: {
...
fallback: {
// Here paste
crypto: require.resolve("crypto-browserify"),


}
}
}
}

Note: Is possible you need other packages how "stream-browserify" the steps are same. This solution works, but when the webpack project starts it shows warnings

Pd: I am not native speaker English, but I hope understand me.

小开

I ended up going into

node_modules/react-scripts/config/webpack.config.js

and adding:

fallback: {
// Here paste
crypto: require.resolve("crypto-browserify"),
https: require.resolve("https-browserify"),
http: require.resolve("stream-http"),
url : require.resolve("url")
}

And now my react app builds with errors but no dependency issues. Ill update this when I get it building.

小开

Add

npm install crypto-js

Or Add a specific version according to your project need

npm install crypto-js@4.0.0

Also, run the above commands in Window "run as administrator" or in Linux use sudo

小开

Alot of answers already but still none of them works. In my case I see warning message


BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default. This is no longer the case. Verify if you need this module and configure a polyfill for it.  If you want to include a polyfill, you need to:         - add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'         - install 'crypto-browserify' If you don't want to include a polyfill, you can use an empty module like this:         resolve.fallback: { "crypto": false }

comment from @stewii did helped me to resolved this.

There is now an ES modules version called "crypto-es". It clears these warnings. npmjs.com/package/crypto-es

After this I imported cryptoES

import CryptoES from 'crypto-es';

and remove the existing import of cryptoJs. Re-start the compile and Voila.. The warning message is gone.

小开

I tried a lot of the solutions above but the final thing that worked for me was downloading the crypto-es package and adding, "type":"module" to package.json.

https://www.npmjs.com/package/crypto-es

小开

I was facing same issue, Just run node patch.js and it worked. The issue is, browser doesn't allow server files to be run on browser. In case you need some of these, You can use node patch.js. If you don't want to run any server file on browser, you can simply apply above mentioned solution by @R.Richards. Might be helpful for someone..

小开

My Error

In my Case the import { get } from "express/lib/response" is the culprit, which is automatically added by vs-code. So, after removing it I solved my issue

小开

When using #Laravel framework with Laravel Mix this is going to be more trick. I spend some hours on this NPM nightmare and found a solid solution.

So, in your webpack.mix.js you find the 'comment'

/*
|--------------------------------------------------------------------------
| Mix Asset Management
|--------------------------------------------------------------------------
|
| Mix provides a clean, fluent API for defining some Webpack build steps
| for your Laravel application. By default, we are compiling the Sass
| file for the application as well as bundling up all the JS files.
|
*/

Now just below that comment add the following lines;

mix.webpackConfig(webpack => {
return {
plugins: [
new webpack.LoaderOptionsPlugin({
exports: {
resolve: {
fallback: {
crypto: require.resolve('crypto-browserify'),
}
}
}
})
]
};
});

Now you can use Laravel Mix just like you would edit webpack.config.js ;) Also; In package.json remove:

--no-progress --hide-modules

These are no longer valid for WebPack >= 5. Enjoy!