github-pages-deploy-action/node_modules/jest-serializer/package.json
2020-03-21 17:13:25 -04:00

54 lines
1.8 KiB
JSON

{
"_args": [
[
"jest-serializer@25.1.0",
"/Users/ives/Documents/Dev/Personal/gh-pages-github-action"
]
],
"_development": true,
"_from": "jest-serializer@25.1.0",
"_id": "jest-serializer@25.1.0",
"_inBundle": false,
"_integrity": "sha512-20Wkq5j7o84kssBwvyuJ7Xhn7hdPeTXndnwIblKDR2/sy1SUm6rWWiG9kSCgJPIfkDScJCIsTtOKdlzfIHOfKA==",
"_location": "/jest-serializer",
"_phantomChildren": {},
"_requested": {
"type": "version",
"registry": true,
"raw": "jest-serializer@25.1.0",
"name": "jest-serializer",
"escapedName": "jest-serializer",
"rawSpec": "25.1.0",
"saveSpec": null,
"fetchSpec": "25.1.0"
},
"_requiredBy": [
"/jest-haste-map"
],
"_resolved": "https://registry.npmjs.org/jest-serializer/-/jest-serializer-25.1.0.tgz",
"_spec": "25.1.0",
"_where": "/Users/ives/Documents/Dev/Personal/gh-pages-github-action",
"bugs": {
"url": "https://github.com/facebook/jest/issues"
},
"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": ">= 8.3"
},
"gitHead": "170eee11d03b0ed5c60077982fdbc3bafd403638",
"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": "25.1.0"
}