chai VS crypto-js

Let's configure tests with mocha, chai and sinon on Typescript in a few steps.

These options totally depend on your requirements. For example an empty hardhat option is a very basic project sample if you need more libraries, plugins or you use Typescript later, you have to add them manually. Like @nomiclabs/hardhat-waffle , [ethereum-waffle](https://www.npmjs.com/package/ethereum-waffle), chai , @nomiclabs/hardhat-ethers , ethers , [@openzeppelin/contracts](https://www.npmjs.com/package/@openzeppelin/contracts) Because, they'll allow us to interact with Ethereum and to test our contracts.

For those of you wondering what a "Chaijs" is like I was: https://github.com/chaijs/chai

> BDD / TDD assertion framework for node.js and the browser that can be paired with any testing framework.

ES6 test setup with Mocha and Chai.

It'd be hard for me to imagine what would it be like back then to write tests if it wasn't for Enzyme. Even with Enzyme, it was noticeably harder than it is today, and I still vividly remember installing and configuring in my project Mocha, Chai, Sinon, and JSDOM, to get pretty much the same tooling that today a single library - Jest - provides out of the box, while adding numerous features on top of that.

The library offers a BDD testing style and fully exploits javascript promises - the resulting tests are simple, clear and expressive. Chakram is built on node.js, mocha, chai and request.

For this example, I am using Mocha, plus Chai for its BDD expect syntax and the chai-as-promised plugin for asynchronous matchers.

chai

The default settings seem to be at fault here, not the implementation it self.

> This is because it both defaults to SHA1, a cryptographic hash algorithm considered insecure since at least 2005, and defaults to one single iteration, a 'strength' or 'difficulty' value specified at 1,000 when specified in 1993

The fix: https://github.com/brix/crypto-js/commit/421dd538b2d34e7c24a...

crypto-js

CryptoJS 官方說明文件：GitHub。

You might use the .env file, which sits inside a server, to store important passwords and keys to databases and APIs. Keeping it in text inside a .env is risky as it may get exposed if the server is compromised. To avoid this issue, one should use Encryption and Decryption. There are a couple of tools and libraries which offer similar functionality. You can try any of those, but we recommend using CryptoJS or Forge.

Edit: They are likely using this version: https://github.com/brix/crypto-js/releases/tag/3.1.5

The Crypto-JS library should be able to decode this. The docs show a simple method, and I'm using it like so:

crypto-js

I kept searching and stumbled accross Staticrypt. This looked pretty promising. This is based on the crypto.js library and will take a full HTML page and encrypt it. The user will then need to enter the password for the script to un-encrypt it. It sounded pretty neat. I plugged in some HTML code and a password to the site to test it out, and sure enough, it spat out an encrypted page. It looked promising enough to look further into.

Don't even have to change any logic just encrypt on write and decrypt on read with something like this: https://github.com/brix/crypto-js