github-pages-deploy-action/node_modules/jest-serializer/package.json
2020-03-31 08:42:07 -04:00

60 lines
1.9 KiB
JSON

{
"_from": "jest-serializer@^25.2.1",
"_id": "jest-serializer@25.2.1",
"_inBundle": false,
"_integrity": "sha512-fibDi7M5ffx6c/P66IkvR4FKkjG5ldePAK1WlbNoaU4GZmIAkS9Le/frAwRUFEX0KdnisSPWf+b1RC5jU7EYJQ==",
"_location": "/jest-serializer",
"_phantomChildren": {},
"_requested": {
"type": "range",
"registry": true,
"raw": "jest-serializer@^25.2.1",
"name": "jest-serializer",
"escapedName": "jest-serializer",
"rawSpec": "^25.2.1",
"saveSpec": null,
"fetchSpec": "^25.2.1"
},
"_requiredBy": [
"/jest-haste-map"
],
"_resolved": "https://registry.npmjs.org/jest-serializer/-/jest-serializer-25.2.1.tgz",
"_shasum": "51727a5fc04256f461abe0fa024a022ba165877a",
"_spec": "jest-serializer@^25.2.1",
"_where": "/Users/ives/Documents/Dev/Personal/gh-pages-github-action/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.",
"devDependencies": {
"@types/node": "*"
},
"engines": {
"node": ">= 8.3"
},
"gitHead": "a679390828b6c30aeaa547d8c4dc9aed6531e357",
"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.2.1"
}