sartography
/
bpmn-js
mirror of https://github.com/sartography/bpmn-js.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
bpmn-js/package.json

69 lines
1.8 KiB
JSON
Raw Normal View History

chore(project): initial import
2014-03-11 14:54:36 +00:00
{
fix(package.json): correct project name
2014-04-08 12:09:04 +00:00
"name": "bpmn-js",
chore(project): release v0.4.1
2014-08-06 13:22:18 +00:00
"version": "0.4.1",
chore(project): initial import
2014-03-11 14:54:36 +00:00
"description": "A bpmn 2.0 toolkit and web modeler",
"scripts": {
"test": "grunt test"
},
"repository": {
"type": "git",
"url": "https://github.com/bpmn-io/bpmn-js"
},
"keywords": [
"bpmn",
"toolkit",
"web modeler",
"modeler",
"modeling",
"process modeling"
],
"author": {
"name": "Nico Rehwaldt",
"url": "https://github.com/Nikku"
},
"contributors": [
{
"name": "bpmn.io contributors",
"url": "https://github.com/bpmn-io"
}
],
chore(project): update dependencies
2014-05-08 06:51:22 +00:00
"license": "http://bpmn.io/license",
chore(project): initial import
2014-03-11 14:54:36 +00:00
"devDependencies": {
chore(project): remove browserify bundle Bundling must be done by users of the library in some way anyway. All those that do not bundle it will use the bower version. Removing the bundle function to keep the build slim.
2014-08-21 13:34:37 +00:00
"brfs": "^1.2.0",
"diagram-js": "^0.4.0",
feat(bower): use exposify to build bower bundle This commit uses exposify to perform a quick replace on web dependency require() statements before browserify can process them. This way we access our external dependencies (jquery, lodash, snapsvg, sax) via window globals in a standalone bower bundle. Closes #63
2014-06-13 14:55:31 +00:00
"exposify": "https://github.com/Nikku/exposify/archive/v0.2.0-transform-arguments-0.tar.gz",
chore(package.json): update dependencies
2014-08-05 06:15:54 +00:00
"grunt": "^0.4.4",
"grunt-browserify": "^2.1.2",
"grunt-contrib-jshint": "^0.7.2",
fix(build): correctly generate source maps
2014-08-06 07:30:02 +00:00
"grunt-contrib-uglify": "https://github.com/gruntjs/grunt-contrib-uglify/archive/master.tar.gz",
chore(package.json): update dependencies
2014-08-05 06:15:54 +00:00
"grunt-jsdoc": "^0.5.1",
"grunt-karma": "^0.8.0",
"grunt-release": "^0.7.0",
chore(tests): use jasmine-test-container-support for test execution This allows us to have tests nice and easily rendered within test-local containers, including captions, status highlighting and links.
2014-06-18 09:45:30 +00:00
"jasmine-test-container-support": "0.0.1",
feat(bower): use exposify to build bower bundle This commit uses exposify to perform a quick replace on web dependency require() statements before browserify can process them. This way we access our external dependencies (jquery, lodash, snapsvg, sax) via window globals in a standalone bower bundle. Closes #63
2014-06-13 14:55:31 +00:00
"jsondiffpatch": "^0.1.7",
chore(project): cleanup dependencies
2014-06-14 11:09:05 +00:00
"karma": "^0.12.12",
chore(package.json): update dependencies
2014-08-05 06:15:54 +00:00
"karma-bro": "^0.6.2",
chore(project): cleanup dependencies
2014-06-14 11:09:05 +00:00
"karma-chrome-launcher": "^0.1.2",
"karma-firefox-launcher": "^0.1.3",
"karma-ie-launcher": "^0.1.4",
feat(bower): use exposify to build bower bundle This commit uses exposify to perform a quick replace on web dependency require() statements before browserify can process them. This way we access our external dependencies (jquery, lodash, snapsvg, sax) via window globals in a standalone bower bundle. Closes #63
2014-06-13 14:55:31 +00:00
"karma-jasmine": "https://github.com/Nikku/karma-jasmine/archive/jasmine-v2.0.0-latest-1.tar.gz",
chore(project): cleanup dependencies
2014-06-14 11:09:05 +00:00
"karma-phantomjs-launcher": "^0.1.2",
chore(package.json): update dependencies
2014-08-05 06:15:54 +00:00
"load-grunt-tasks": "^0.3.0",
chore(project): remove browserify bundle Bundling must be done by users of the library in some way anyway. All those that do not bundle it will use the bower version. Removing the bundle function to keep the build slim.
2014-08-21 13:34:37 +00:00
"time-grunt": "^0.3.2"
chore(project): initial import
2014-03-11 14:54:36 +00:00
},
"dependencies": {
chore(project): remove browserify bundle Bundling must be done by users of the library in some way anyway. All those that do not bundle it will use the bower version. Removing the bundle function to keep the build slim.
2014-08-21 13:34:37 +00:00
"bpmn-moddle": "^0.3.0",
"diagram-js-direct-editing": "^0.3.0",
"didi": "^0.0.4",
"jquery": "^2.1.0",
"jquery-mousewheel": "^3.1.11",
"lodash": "^2.4.0",
feat(modeling): validate + create unique ids This adds id logging + validation to the Modeler. As a result the modeler will throw hard exeptions on colliding id mappings and may generated unique ids. Related to bpmn-io/bpmn-js#92
2014-08-04 14:34:37 +00:00
"object-refs": "^0.1.0",
chore(project): remove browserify bundle Bundling must be done by users of the library in some way anyway. All those that do not bundle it will use the bower version. Removing the bundle function to keep the build slim.
2014-08-21 13:34:37 +00:00
"ids": "^0.0.3",
feat(Modeler): include bpmn-js-cli
2014-08-08 12:42:50 +00:00
"bpmn-js-cli": "^0.1.1"
},
"peerDependencies": {
chore(project): remove browserify bundle Bundling must be done by users of the library in some way anyway. All those that do not bundle it will use the bower version. Removing the bundle function to keep the build slim.
2014-08-21 13:34:37 +00:00
"diagram-js": "^0.4.0"
chore(project): initial import
2014-03-11 14:54:36 +00:00
}
}