flowhub / flowhub-registry Goto Github PK

View Code? Open in Web Editor NEW

14.0 8.0 5.0 126 KB

Library for dealing with the Flowhub Runtime Registry

Home Page: http://flowhub.io

JavaScript 100.00%

fbp flowhub

flowhub-registry's People

Contributors

Stargazers

Watchers

Forkers

meticulo3366 forresto ensonic mathieub93 mfkiwl

flowhub-registry's Issues

An in-range update of grunt-noflo-browser is breaking the build 🚨

Version 1.4.0 of grunt-noflo-browser was just published.

Branch	Build failing 🚨
Dependency	grunt-noflo-browser
Current Version	1.3.2
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

grunt-noflo-browser 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.

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build failed Details

Commits

The new version differs by 8 commits.

49cbe83 Bump
f6ac38e Merge pull request #30 from noflo/noflo_component_loader
9935b00 Try to match also Windows paths with regexp
c188098 Bump noflo-component-loader dep
84cec54 Update to legacy-free component versions
821de79 Test on modern Node.js
ea16584 Use noflo-component-loader to build the loader
f00089b Remove obsolete grunt-noflo-manifest

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

export defaults?

do we want to export the defaults and add remaining ones here:
https://github.com/the-grid/flowhub-registry/blob/master/index.js#L2-4

this can be used in
https://github.com/noflo/noflo-nodejs/blob/master/index.coffee#L17-36
to avoid hardcoding the defaults.

An in-range update of grunt is breaking the build 🚨

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

The devDependency grunt was updated from `1.0.4` to `1.1.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt 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.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Release Notes for v1.1.0

Update to mkdirp ~1.0.3
Only support versions of Node >= 8

Commits

The new version differs by 8 commits.

d5cdac0 Merge pull request #1706 from gruntjs/tag-neew
4674c59 v1.1.0
6124409 Merge pull request #1705 from gruntjs/mkdirp-update
0a66968 Fix up Buffer usage
4bfa98e Support versions of node >= 8
f1898eb Update to mkdirp ~1.0.3
75da17b HTTPS link to gruntjs.com (#1683)
6795d31 Update js-yaml dependecy to ~3.13.1 (#1680)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

flowhub / flowhub-registry Goto Github PK

flowhub-registry's People

Contributors

Stargazers

Watchers

Forkers

flowhub-registry's Issues

An in-range update of grunt-noflo-browser is breaking the build 🚨

Version 1.4.0 of grunt-noflo-browser was just published.

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

export defaults?

An in-range update of grunt is breaking the build 🚨

The devDependency grunt was updated from `1.0.4` to `1.1.0`.

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

flowhub / flowhub-registry Goto Github PK

flowhub-registry's People

Contributors

Stargazers

Watchers

Forkers

flowhub-registry's Issues

Version 1.4.0 of grunt-noflo-browser was just published.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

The devDependency grunt was updated from 1.0.4 to 1.1.0.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency grunt was updated from `1.0.4` to `1.1.0`.