noflo / noflo-html

HTML handling components for NoFlo

HTML components for NoFlo

This module provides HTML processing components for the NoFlo flow-based programming framework

noflo-html's Issues

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

Version 3.3.0 of grunt-contrib-uglify was just published.

Branch	Build failing 🚨
Dependency	grunt-contrib-uglify
Current Version	3.2.1
Type	devDependency

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

grunt-contrib-uglify 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 could not complete due to an error Details

---

Commits

The new version differs by 5 commits.

• e7915ce v3.3.0.
• bf23f0b Lock grunt-contrib-internal to v1.3.0.
• 6db68bd upgrade to uglify-js 3.3.0
• 04494d9 Update docs/uglify-options.md.
• 263196c Add a Git .mailmap with my new name (#497)

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 🌴

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 🌴

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
• The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

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 🌴

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

Version 0.8.0 of noflo just got published.

Branch	Build failing 🚨
Dependency	noflo
Current Version	0.7.9
Type	dependency

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

As noflo 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 💪

---

Status Details

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

Commits

The new version differs by 325 commits (ahead by 325, behind by 2).

• a1187c6 Bump
• d1c13f2 Update Flowhub docs link
• 49cfb8b Update fbp-protocol link
• b25001e Update MsgFlo link
• 9757b8d Merge pull request #534 from noflo/update_copyrights
• f84ca06 Reassign copyrights
• a790ba4 Make 'grunt test' run the build task instead of duplicating
• 593a39d Bump
• 05d38ad Document WirePattern Process API changes, refs #526
• 452c57f Merge pull request #526 from noflo/process_wirepattern
• 6ceab6f Merge pull request #532 from noflo/fix_null_undefined
• efaba77 Fix ip.data turned from null to undefined
• 76d10c6 Provide postpone/resume functions that throw a more user-friendly error
• 4db7e7b Plug deprecation warnings back in
• 9d15d3c Collation support for WirePattern group and field options in Process API

There are 250 commits in total. See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴

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 🌴

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

Version 2.3.0 of grunt-contrib-uglify just got published.

Branch	Build failing 🚨
Dependency	grunt-contrib-uglify
Current Version	2.2.1
Type	devDependency

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

As grunt-contrib-uglify 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 💪

---

Status Details

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

Commits

The new version differs by 2 commits .

• f3086c1 v2.3.0.
• 7dc5e1d Log fixes. (#454) r=vladikoff

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

---

Your Greenkeeper Bot 🌴