🌇 🌆 🌉 Advanced, user-friendly, language-agnostic, super-high-performance test runner. http://sumanjs.org
License: MIT License
This is not the project your looking for. This is simply a dummy placeholder repo which can direct people to the correct one.
The repos you are looking for are here:
![greenkeeper[bot] avatar](https://avatars.githubusercontent.com/in/505?v=4 "greenkeeper[bot]")
Hey there,
I really like the idea behind the lib.
I decided to try and convert our current mocha tests to suman but immediately ran into error using suman.
mkdir bla
cd bla
npm install -g suman
suman --init
=> Suman uncaught exception =>
Error: Cannot find module 'suman-utils/utils'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object.<anonymous> (/Users/____/.nvm/versions/node/v4.4.5/lib/node_modules/suman/lib/utils.js:1:80)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
i'm using nvm and i tried on both node v4.4.5 and v6.2.2
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/node |
| Current Version | 7.0.13 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | systemjs-builder |
| Current Version | 0.16.7 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As systemjs-builder is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
First-stage dynamic import support.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
https://github.com/kevva/executable/blob/master/index.js
const fs = require('fs');
console.log(process.argv);
fs.open(__filename, 'r+', function(err, fd){
if(err) throw err;
const b = Buffer.alloc(4);
fs.read(fd, b, 0, 4, 0, function(err, bytesRead, buffer){
if(err) throw err;
console.log('data: ', bytesRead);
console.log('buffer: ', String(buffer));
});
});The example blog post listed in the readme (https://medium.com/@the1mills/introducing-suman-a-node-js-testing-library-20fdae524cd) has been deleted and returns a 410.
see:
let generatedBashCode = dashdash.bashCompletionFromOptions({
name: 'check-git-status',
options: options,
includeHidden: true
});| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/node |
| Current Version | 7.0.12 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Hi!
I've just created http://npm.im/function-arguments that also supports ES2015 - generator functions, regular functions and arrow functions. And because i review you project I seen that you just use .args property from parse-function, so you can replace it with the other package.
This will also give performance bump, because not using acorn. And really acorn is not needed for arguments - http://npm.im/orientjs and http://npm.im/karma-server-side are good example when you need parse-function.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/core-js |
| Current Version | 0.9.42 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/core-js is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | webpack |
| Current Version | 2.3.3 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As webpack is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
import() now allows to configure a chunk nameimport(/* webpackChunkName: "my-chunk-name" */ "module")
require.ensure has a error callbackrequire.ensure([], () => { require("a"); }, err => { console.error("We failed to load chunk: " + err); }, "chunk-name");
warningsFilter to stats options to filter warnings__webpack_chunkname__ to ExtendedAPIPluginNamedChunksPlugin which allows to set chunk id, i. e. to chunk namerequire.ensureimport()The new version differs by 252 commits .
0cbd8fd 2.4.0ab22702 Merge pull request #4507 from ts-webpack/refactor/clean-codee787452 Merge pull request #4700 from webpack/bug/future-var-declaration98153f5 Merge pull request #4706 from webpack/test/parser-coverage52f2daf add test cases and fix a buge4b8833 improve code coverage3afe67d add parser prewalking to capture scope0990915 spacingd8a8bd3 deprecate string option instead of removing itdbc40e8 Merge pull request #4698 from simon04/examples-source-map0ef0581 Add example demonstrating all source-map variantsa822784 Merge pull request #4696 from webpack/bugfix/parser-refactoringba3688a fixes misstake while es6 refactoring, add support for other variable declarations07f6281 fix: typos and variables/function misuse52055ba refactor: dead code eliminationThere are 250 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/chai |
| Current Version | 4.0.1 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/chai is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | socket.io |
| Current Version | 1.7.3 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
socket.io is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
The new version differs by 4 commits ahead by 4, behind by 2.
0abbd4d [chore] Release 1.7.4c89ccd9 [chore] Bump engine.io to version 1.8.4a646044 [chore] Release 1.7.3751a6fc [chore] Bump engine.io to version 1.8.3false
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | v8flags |
| Current Version | 2.0.12 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
As v8flags is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | webpack |
| Current Version | 2.4.1 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As webpack is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
hashSalt to schemasourceMappingURL, which caused issues with some toolsThe new version differs by 81 commits0.
bf3652b 2.5.0cd1cd29 Merge pull request #4815 from webpack/bugfix/extract-async-initialb45588b CommonsChunkPlugin in async mode doesn't select initial chunks8bab88c Merge pull request #4814 from webpack/test/move-entrya244879 add testcase for moving entry modules into the commons chunk85dc98f Merge pull request #4813 from JLHwung/perf/date-now6afc397 perf: use Date.now() instead of new Date().getTime()94d0641 perf: use Date.now() instead of +new Date()c91ba49 Merge pull request #4791 from deificx/master94ba75f Merge pull request #4794 from ndresx/disable-manifest-json-pretty-print84ea1ff added error to stats.moduleTrace test name to trigger test cases corretly8ad4386 test cases for stats.moduleTrace option958156a moduleTrace added to webpackOptionsSchema.jsonde87f93 Disable manifest.json pretty print4131013 rename stats.stackTrace to stats.moduleTraceThere are 81 commits in total.
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
https://www.quora.com/Is-there-a-way-to-type-check-JSON-with-TypeScript/answer/Tim-Mensch?srid=Xt2o
Yes, I'm doing exactly that in one of my projects.
What you're looking for is called a JSON schema. I've been using this library to generate the schema as a build step:
YousefED/typescript-json-schema (https://github.com/YousefED/typescript-json-schema)
Then as another build step I validate the JSON with tv4:
geraintluff/tv4 (https://github.com/geraintluff/tv4)
More specifically, I use gulp to build and validate everything. Since all of that logic is in one file in my code, and I don't mind sharing it, I've stuck it into a gist here:
Validation of JSON based on a TypeScript declaration (https://gist.github.com/TimMensch/45df32352b9d32353ab8b5912362632b)
In the main gulpfile, I require the above and use it like:
generateAndValidate("actors-lint", "ActorSpecArray", paths.actors);
Where “actors-lint” is the name of the gulp task to create, “ActorSpecArray” is the name of the type, and paths.actors is a wildcard of the JSON files to validate.
Let me know if this seems useful and I can cram it into an npm package.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/async |
| Current Version | 2.0.43 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/async is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | require-from-string |
| Current Version | 1.2.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
require-from-string is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
The new version differs by 3 commits.
b81e995 1.2.18561059 Merge pull request #6 from 60frames/module80783b2 Require 'module' instead of referencing constructorSee the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | tap-parser |
| Current Version | 5.3.3 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
tap-parser is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | rimraf |
| Current Version | 2.6.1 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
rimraf is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/lodash |
| Current Version | 4.14.62 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/lodash is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
maybe try this
| Branch | Build failing 🚨 |
|---|---|
| Dependency | async |
| Current Version | 2.4.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
async is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | babel-polyfill |
| Current Version | 6.23.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As babel-polyfill is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | rxjs |
| Current Version | 5.3.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As rxjs is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | sqlite3 |
| Current Version | 3.1.9 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
sqlite3 is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
The new version differs by 7 commits.
68c65f3 bump to 3.1.10 [publish binary]98a79b8 add back branches [publish binary]748119a [publish binary]515f650 Drop node v0.12 support, upgrade nan to latest68c5666 bump to v3.1.10-alpha [publish binary]5d2e111 avoid #861 from happening again by adding to npmignores34e1a40 prepublish is deprecated in npm@5See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/async |
| Current Version | 2.0.40 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/async is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/socket.io |
| Current Version | 1.4.29 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/socket.io is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Error: Cannot find module 'color-convert'
at Function.Module._resolveFilename (module.js:485:15)
at Function.Module._load (module.js:437:25)
at Module.require (module.js:513:17)
at require (internal/module.js:11:18)
at Object.<anonymous> (/home/oleg/WebstormProjects/oresoftware/sumanjs/suman-reporters/node_modules/ansi-styles/index.js:2:22)
at Module._compile (module.js:569:30)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:503:32)
at tryModuleLoad (module.js:466:12)
at Function.Module._load (module.js:458:3)
| Branch | Build failing 🚨 |
|---|---|
| Dependency | bluebird |
| Current Version | 3.5.0 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As bluebird is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Bugfixes:
The new version differs by 26 commits.
dcfa52b Release v3.5.148c8591 Fixes #14043c93a91 Revert "Update default.html"5155a7b Merge pull request #1463 from gabegorelick/isError3f7ccf4 Better error checkf8f4a01 Merge pull request #1462 from themez/patch-118891c9 Fix title styleb2b14c2 Update default.htmla61aa1c tiny grammar change (#1457)2c9f7a4 Update tap.md (#1438)3a7fcbb fixes markdow headers (#1437)e889c0d Correct a tiny tiny typo (#1431)e03f12c improve .all() docs (#1436)4f90934 Updated links (#1420)3d2e57f Add Node.js 7+8 to Travis build matrix (#1412)There are 26 commits in total.
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | chai |
| Current Version | 4.1.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
chai is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
This release includes a few bug and documentation fixes.
.instanceof to allow DOM interfaces in IE11 (#1000, #1008; @meeber).include to work with all objects (#1009, #1012; @meeber)The new version differs by 10 commits.
02ddebd Merge pull request #1019 from meeber/release-4.1.1ac48db3 [email protected]d2e9599 Merge pull request #1016 from chaijs/fix-reindent-code-101492d2cca docs: re-indent hasAnyKeys codeb625497 Merge pull request #1012 from meeber/fix-include-types8fa24f2 Merge pull request #1014 from zenHeart/fix-hasAnyKeys-comment113a5b8 fix: correct hasAnyKeys comment errorc01cf30 fix: .include to work with all objects1847ef8 Merge pull request #1008 from meeber/fix-ie11-instanceofc107abb fix: .instanceof to allow DOM interfaces in IE11See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/lodash |
| Current Version | 4.14.63 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/lodash is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/socket.io |
| Current Version | 1.4.30 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/socket.io is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | replacestream |
| Current Version | 4.0.2 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
replacestream is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
The new version differs by 5 commits.
8517483 4.0.3838e2a4 Fixed incorrect tail handling caused by missing .length (#30)c43b1e7 run CI with more modern Node.js8e2831e update devDependencies9ceb058 add martin as a contributor update package.json with latest versionSee the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/socket.io-client |
| Current Version | 1.4.29 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/socket.io-client is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | semver |
| Current Version | 5.3.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
semver is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
The new version differs by 16 commits.
e1c49c8 v5.4.03ebc11d more test coverage5b30513 speed up tests a lot, add coveragee1668ce add top level intersects function6cb2bcb intersection: use semver.version, not semver.raw4bacbfa Make exposed apis more clear8b86a26 Reduce line length and remove unused platform parameter99f133e Add range and comparator intersection docs to READMEafbe8ca Move methods to comparator and range67c9ed7 Add support for range and comparators comparisoncaeeac4 remove 0.x from Travis, cache npm stuff, use containersbdda1a4 Add Node.js 8 to .travis.yml8fff305 Add node 6 to travisaaba710 Added syntax highlighting to readme example32802c5 minimize heap allocations for maxSatisfying/minSatisfyingThere are 16 commits in total.
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | systemjs-builder |
| Current Version | 0.16.4 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As systemjs-builder is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
Features
esModule meta option to be supported in bundles and builds (#775).Bug fixes
The new version differs by 12 commits.
5e84be0 0.16.55954637 update sfx template4cd3696 upgrade transformers for ensuring non-duplicate esModule detection4240719 revert uglify3eaf589 pass through esModule meta option to compiler802ab43 es-module build supportbd48287 tmp disable node 4 build219d7d1 update to new default interopdfbb3c4 Merge pull request #798 from papandreou/fix/encodeNamesCheckde2f05b Fix bad defaults.encodeNames check.28cefe0 Merge pull request #789 from thatJavaNerd/patch-1af26fda Fix markdown link to documentationSee the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
use these, after they are backported to nodejs version 6,7 etc.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | async |
| Current Version | 2.3.0 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
async is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | systemjs-builder |
| Current Version | 0.16.8 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As systemjs-builder is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
__useDefault fixes corresponding to SystemJS 0.20.14
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Ok, I think this is what you mean: https://developers.google.com/chart/interactive/docs/gallery/timeline
yeah that's probably a lot better..my processes are always independent, whereas Gantt charts have process that are interdependent...thanks!
original issue:
GoogleWebComponents/google-chart#194 (comment)
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/node |
| Current Version | 7.0.16 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | @types/socket.io-client |
| Current Version | 1.4.30 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
@types/socket.io-client is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
| Branch | Build failing 🚨 |
|---|---|
| Dependency | socket.io-client |
| Current Version | 1.7.3 |
| Type | dependency |
This version is covered by your current version range and after updating it in your project the build failed.
socket.io-client is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Imagine I have this simple scenario:
export class A {
constructor(){
}
foo() : A {
return this;
}
}
export class B extends A {
constructor(){
}
bar() : B {
return this;
}
}
if I do this:
new B().foo().bar()
I will get a TypeError saying that bar() is not a function. Is the only way to do this, to override the method in the superclass? Must I do this?
export class B extends A {
constructor(){
}
foo(): B { // override foo so it returns B
return this;
}
bar() : B {
return this;
}
}
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.