taler/wallet-core
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Activity
d6bf24902a
wallet-core/node_modules/core-js/package.json

59 lines
1.5 KiB
JSON
Raw Normal View History

add node_modules to address #4364
2016-10-10 03:43:44 +02:00
{
node_modules
2016-11-03 01:33:53 +01:00
"name": "core-js",
add node_modules to address #4364
2016-10-10 03:43:44 +02:00
"description": "Standard library",
Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
2017-04-20 03:09:25 +02:00
"version": "1.2.7",
node_modules
2016-11-03 01:33:53 +01:00
"repository": {
"type": "git",
"url": "https://github.com/zloirock/core-js.git"
},
"main": "index.js",
add node_modules to address #4364
2016-10-10 03:43:44 +02:00
"devDependencies": {
Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
2017-04-20 03:09:25 +02:00
"webpack": "1.12.x",
add node_modules to address #4364
2016-10-10 03:43:44 +02:00
"LiveScript": "1.3.x",
Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
2017-04-20 03:09:25 +02:00
"grunt": "0.4.x",
"grunt-cli": "0.1.x",
"grunt-livescript": "0.5.x",
"grunt-contrib-uglify": "0.10.x",
"grunt-contrib-watch": "0.6.x",
"grunt-contrib-clean": "0.6.x",
"grunt-contrib-copy": "0.8.x",
"grunt-karma": "0.12.x",
"karma": "0.13.x",
"karma-qunit": "0.1.x",
"karma-chrome-launcher": "0.2.x",
"karma-ie-launcher": "0.2.x",
"karma-firefox-launcher": "0.1.x",
"karma-phantomjs-launcher": "0.2.x",
add node_modules to address #4364
2016-10-10 03:43:44 +02:00
"promises-aplus-tests": "2.1.x",
Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
2017-04-20 03:09:25 +02:00
"eslint": "1.9.x",
"qunitjs": "1.23.x",
"phantomjs": "1.9.x"
add node_modules to address #4364
2016-10-10 03:43:44 +02:00
},
node_modules
2016-11-03 01:33:53 +01:00
"scripts": {
"grunt": "grunt",
Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
2017-04-20 03:09:25 +02:00
"lint": "eslint es5 es6 es7 js web core fn modules",
node_modules
2016-11-03 01:33:53 +01:00
"promises-tests": "promises-aplus-tests tests/promises-aplus/adapter",
Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
2017-04-20 03:09:25 +02:00
"test": "npm run lint && npm run grunt livescript client karma:continuous library karma:continuous-library && npm run promises-tests && lsc tests/commonjs"
add node_modules to address #4364
2016-10-10 03:43:44 +02:00
},
node_modules
2016-11-03 01:33:53 +01:00
"license": "MIT",
add node_modules to address #4364
2016-10-10 03:43:44 +02:00
"keywords": [
"ES5",
"ECMAScript 5",
"ES6",
"ECMAScript 6",
"ES7",
"ECMAScript 7",
"Harmony",
"Strawman",
"Map",
"Set",
"WeakMap",
"WeakSet",
"Promise",
"Symbol",
Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
2017-04-20 03:09:25 +02:00
"Array generics",
add node_modules to address #4364
2016-10-10 03:43:44 +02:00
"setImmediate",
"Dict",
Reorganize module loading. We now use webpack instead of SystemJS, effectively bundling modules into one file (plus commons chunks) for every entry point. This results in a much smaller extension size (almost half). Furthermore we use yarn/npm even for extension run-time dependencies. This relieves us from manually vendoring and building dependencies. It's also easier to understand for new developers familiar with node.
2017-04-20 03:09:25 +02:00
"partial application"
node_modules
2016-11-03 01:33:53 +01:00
]
}
Reference in New Issue Copy Permalink