121 lines
12 KiB
JSON
121 lines
12 KiB
JSON
|
{
|
|||
|
|
"_args": [
|
|||
|
|
[
|
|||
|
|
{
|
|||
|
|
"raw": "json5@^0.5.0",
|
|||
|
|
"scope": null,
|
|||
|
|
"escapedName": "json5",
|
|||
|
|
"name": "json5",
|
|||
|
|
"rawSpec": "^0.5.0",
|
|||
|
|
"spec": ">=0.5.0 <0.6.0",
|
|||
|
|
"type": "range"
|
|||
|
|
},
|
|||
|
|
"/home/jdaugherty/work/GT2/GT2-Android/node_modules/@expo/json-file"
|
|||
|
|
]
|
|||
|
|
],
|
|||
|
|
"_from": "json5@>=0.5.0 <0.6.0",
|
|||
|
|
"_id": "json5@0.5.1",
|
|||
|
|
"_inCache": true,
|
|||
|
|
"_location": "/json5",
|
|||
|
|
"_nodeVersion": "6.9.1",
|
|||
|
|
"_npmOperationalInternal": {
|
|||
|
|
"host": "packages-18-east.internal.npmjs.com",
|
|||
|
|
"tmp": "tmp/json5-0.5.1.tgz_1480284434295_0.5308296058792621"
|
|||
|
|
},
|
|||
|
|
"_npmUser": {
|
|||
|
|
"name": "jordanbtucker",
|
|||
|
|
"email": "jordanbtucker@gmail.com"
|
|||
|
|
},
|
|||
|
|
"_npmVersion": "3.10.9",
|
|||
|
|
"_phantomChildren": {},
|
|||
|
|
"_requested": {
|
|||
|
|
"raw": "json5@^0.5.0",
|
|||
|
|
"scope": null,
|
|||
|
|
"escapedName": "json5",
|
|||
|
|
"name": "json5",
|
|||
|
|
"rawSpec": "^0.5.0",
|
|||
|
|
"spec": ">=0.5.0 <0.6.0",
|
|||
|
|
"type": "range"
|
|||
|
|
},
|
|||
|
|
"_requiredBy": [
|
|||
|
|
"/@expo/json-file"
|
|||
|
|
],
|
|||
|
|
"_resolved": "https://registry.npmjs.org/json5/-/json5-0.5.1.tgz",
|
|||
|
|
"_shasum": "1eade7acc012034ad84e2396767ead9fa5495821",
|
|||
|
|
"_shrinkwrap": null,
|
|||
|
|
"_spec": "json5@^0.5.0",
|
|||
|
|
"_where": "/home/jdaugherty/work/GT2/GT2-Android/node_modules/@expo/json-file",
|
|||
|
|
"author": {
|
|||
|
|
"name": "Aseem Kishore",
|
|||
|
|
"email": "aseem.kishore@gmail.com"
|
|||
|
|
},
|
|||
|
|
"bin": {
|
|||
|
|
"json5": "lib/cli.js"
|
|||
|
|
},
|
|||
|
|
"bugs": {
|
|||
|
|
"url": "https://github.com/aseemk/json5/issues"
|
|||
|
|
},
|
|||
|
|
"contributors": [
|
|||
|
|
{
|
|||
|
|
"name": "Max Nanasy",
|
|||
|
|
"email": "max.nanasy@gmail.com"
|
|||
|
|
},
|
|||
|
|
{
|
|||
|
|
"name": "Andrew Eisenberg",
|
|||
|
|
"email": "andrew@eisenberg.as"
|
|||
|
|
},
|
|||
|
|
{
|
|||
|
|
"name": "Jordan Tucker",
|
|||
|
|
"email": "jordanbtucker@gmail.com"
|
|||
|
|
}
|
|||
|
|
],
|
|||
|
|
"dependencies": {},
|
|||
|
|
"description": "JSON for the ES5 era.",
|
|||
|
|
"devDependencies": {
|
|||
|
|
"gulp": "^3.9.1",
|
|||
|
|
"gulp-jshint": "^2.0.1",
|
|||
|
|
"jshint": "^2.9.3",
|
|||
|
|
"jshint-stylish": "^2.2.1",
|
|||
|
|
"mocha": "^3.1.0"
|
|||
|
|
},
|
|||
|
|
"directories": {},
|
|||
|
|
"dist": {
|
|||
|
|
"shasum": "1eade7acc012034ad84e2396767ead9fa5495821",
|
|||
|
|
"tarball": "https://registry.npmjs.org/json5/-/json5-0.5.1.tgz"
|
|||
|
|
},
|
|||
|
|
"files": [
|
|||
|
|
"lib/"
|
|||
|
|
],
|
|||
|
|
"gitHead": "6be6a70e250e6fbbf42db75cd1f6a1aadeeeeb07",
|
|||
|
|
"homepage": "http://json5.org/",
|
|||
|
|
"keywords": [
|
|||
|
|
"json",
|
|||
|
|
"es5"
|
|||
|
|
],
|
|||
|
|
"license": "MIT",
|
|||
|
|
"main": "lib/json5.js",
|
|||
|
|
"maintainers": [
|
|||
|
|
{
|
|||
|
|
"name": "aseemk",
|
|||
|
|
"email": "aseem.kishore@gmail.com"
|
|||
|
|
},
|
|||
|
|
{
|
|||
|
|
"name": "jordanbtucker",
|
|||
|
|
"email": "jordanbtucker@gmail.com"
|
|||
|
|
}
|
|||
|
|
],
|
|||
|
|
"name": "json5",
|
|||
|
|
"optionalDependencies": {},
|
|||
|
|
"readme": "# JSON5 – Modern JSON\n\n[](https://travis-ci.org/json5/json5)\n\nJSON is an excellent data format, but we think it can be better.\n\n**JSON5 is a proposed extension to JSON** that aims to make it easier for\n*humans to write and maintain* by hand. It does this by adding some minimal\nsyntax features directly from ECMAScript 5.\n\nJSON5 remains a **strict subset of JavaScript**, adds **no new data types**,\nand **works with all existing JSON content**.\n\nJSON5 is *not* an official successor to JSON, and JSON5 content may *not*\nwork with existing JSON parsers. For this reason, JSON5 files use a new .json5\nextension. *(TODO: new MIME type needed too.)*\n\nThe code here is a **reference JavaScript implementation** for both Node.js\nand all browsers. It’s based directly off of Douglas Crockford’s own [JSON\nimplementation][json_parse.js], and it’s both robust and secure.\n\n\n## Why\n\nJSON isn’t the friendliest to *write*. Keys need to be quoted, objects and\narrays can’t have trailing commas, and comments aren’t allowed — even though\nnone of these are the case with regular JavaScript today.\n\nThat was fine when JSON’s goal was to be a great data format, but JSON’s usage\nhas expanded beyond *machines*. JSON is now used for writing [configs][ex1],\n[manifests][ex2], even [tests][ex3] — all by *humans*.\n\n[ex1]: http://plovr.com/docs.html\n[ex2]: https://www.npmjs.org/doc/files/package.json.html\n[ex3]: http://code.google.com/p/fuzztester/wiki/JSONFileFormat\n\nThere are other formats that are human-friendlier, like YAML, but changing\nfrom JSON to a completely different format is undesirable in many cases.\nJSON5’s aim is to remain close to JSON and JavaScript.\n\n\n## Features\n\nThe following is the exact list of additions to JSON’s syntax introduced by\nJSON5. **All of these are optional**, and **all of these come from ES5**.\n\n### Objects\n\n- Object keys can be unquoted if they’re valid [identifiers][mdn_variables].\n Yes, even reserved keywords (like `default`) are valid unquoted keys in ES5\n [[§11.1.5](http://es5.github.com/#x11.1.5), [§7.6](http://es5.github.com/#x7.6)].\n ([More info](https://mathiasbynens.be/notes/javascript-identifiers))\n\n *(TODO: Unicode characters and escape sequences aren’t yet supported in this\n implementation.)*\n \n- Object keys can also be single-quoted.\n\n- Objects can have trailing commas.\n\n[mdn_variables]: https://developer.mozilla.org/en/Core_JavaScript_1.5_Guide/Core_Language_Features#Variables\n\n### Arrays\n\n- Arrays can have trailing commas.\n\n### Strings\n\n- Strings can be single-quoted.\n\n- Strings can be split across multiple lines; just prefix each newline with a\n backslash. [ES5 [§7.8.4](http://es5.github.com/#x7.8.4)]\n\n### Numbers\n\n- Numbers can be hexadecimal (base 16).\n\n- Numbers can begin or end with a (leading or trailing) decimal point.\n\n- Numbers can include `Infinity`, `-Infinity`, `NaN`, and `-NaN`.\n\n- Numbers can begin with an explicit plus sign.\n\n### Comments\n\n- Both inline (single-line) and block (multi-line) comments are allowed.\n\n\n## Example\n\nThe following is a contrived example, but it illustrates most of the features:\n\n```js\n{\n foo: 'bar',\n while: true,\n\n this: 'is a \\\nmulti-line string',\n\n // this is an inline comment\n here: 'is another', // inline comment\n\n /* this is a block comment\n that continues on another line */\n\n hex: 0xDEADbeef,\n half: .5,\n delta: +10,\n to: Infinity, // and beyond!\n\n finally: 'a trailing comma',\n oh: [\n \"we shouldn't forget\",\n 'arrays can have',\n 'trailing commas too',\n ],\n}\n```\n\nThis implementation’s own [package.json5](package.json5) is more realistic:\n\n```js\n// This file is written in JSON5 syntax, naturally, but npm needs a regular\n// JSON file, so compile via `npm run build`. Be sure to keep both in sync!\n\n{\n name: 'json5',\n version: '0.5.0',\n description: 'JSON for
|
|||
|
|
"readmeFilename": "README.md",
|
|||
|
|
"repository": {
|
|||
|
|
"type": "git",
|
|||
|
|
"url": "git+https://github.com/aseemk/json5.git"
|
|||
|
|
},
|
|||
|
|
"scripts": {
|
|||
|
|
"build": "node ./lib/cli.js -c package.json5",
|
|||
|
|
"test": "mocha --ui exports --reporter spec"
|
|||
|
|
},
|
|||
|
|
"version": "0.5.1"
|
|||
|
|
}
|