{ "_args": [ [ "jest-serializer@25.5.0", "C:\\Users\\hp\\Desktop\\gitzhongyi" ] ], "_development": true, "_from": "jest-serializer@25.5.0", "_id": "jest-serializer@25.5.0", "_inBundle": false, "_integrity": "sha512-LxD8fY1lByomEPflwur9o4e2a5twSQ7TaVNLlFUuToIdoJuBt8tzHfCsZ42Ok6LkKXWzFWf3AGmheuLAA7LcCA==", "_location": "/jest-serializer", "_phantomChildren": {}, "_requested": { "type": "version", "registry": true, "raw": "jest-serializer@25.5.0", "name": "jest-serializer", "escapedName": "jest-serializer", "rawSpec": "25.5.0", "saveSpec": null, "fetchSpec": "25.5.0" }, "_requiredBy": [ "/jest-haste-map" ], "_resolved": "https://registry.npmmirror.com/jest-serializer/-/jest-serializer-25.5.0.tgz", "_spec": "25.5.0", "_where": "C:\\Users\\hp\\Desktop\\gitzhongyi", "bugs": { "url": "https://github.com/facebook/jest/issues" }, "dependencies": { "graceful-fs": "^4.2.4" }, "description": "Module for serializing and deserializing object into memory and disk. By default, the `v8` implementations are used, but if not present, it defaults to `JSON` implementation. Both serializers have the advantage of being able to serialize `Map`, `Set`, `undefined`, `NaN`, etc, although the JSON one does it through a replacer/reviver.", "devDependencies": { "@types/graceful-fs": "^4.1.3", "@types/node": "*" }, "engines": { "node": ">= 8.3" }, "gitHead": "ddd73d18adfb982b9b0d94bad7d41c9f78567ca7", "homepage": "https://github.com/facebook/jest#readme", "license": "MIT", "main": "build/index.js", "name": "jest-serializer", "publishConfig": { "access": "public" }, "repository": { "type": "git", "url": "git+https://github.com/facebook/jest.git", "directory": "packages/jest-serializer" }, "types": "build/index.d.ts", "typesVersions": { "<3.8": { "build/*": [ "build/ts3.4/*" ] } }, "version": "25.5.0" }