TianmuBackend/node_modules/jest-serializer/package.json

{
  "_from": "jest-serializer@^24.9.0",
  "_id": "jest-serializer@24.9.0",
  "_inBundle": false,
  "_integrity": "sha512-DxYipDr8OvfrKH3Kel6NdED3OXxjvxXZ1uIY2I9OFbGg+vUkkg7AGvi65qbhbWNPvDckXmzMPbK3u3HaDO49bQ==",
  "_location": "/jest-serializer",
  "_phantomChildren": {},
  "_requested": {
    "type": "range",
    "registry": true,
    "raw": "jest-serializer@^24.9.0",
    "name": "jest-serializer",
    "escapedName": "jest-serializer",
    "rawSpec": "^24.9.0",
    "saveSpec": null,
    "fetchSpec": "^24.9.0"
  },
  "_requiredBy": [
    "/jest-haste-map"
  ],
  "_resolved": "https://registry.npmjs.org/jest-serializer/-/jest-serializer-24.9.0.tgz",
  "_shasum": "e6d7d7ef96d31e8b9079a714754c5d5c58288e73",
  "_spec": "jest-serializer@^24.9.0",
  "_where": "E:\\workspace\\cfd-front-admin\\node_modules\\jest-haste-map",
  "bugs": {
    "url": "https://github.com/facebook/jest/issues"
  },
  "bundleDependencies": false,
  "deprecated": false,
  "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.",
  "engines": {
    "node": ">= 6"
  },
  "gitHead": "9ad0f4bc6b8bdd94989804226c28c9960d9da7d1",
  "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",
  "version": "24.9.0"
}