kt3k / gulp-browserify-example

gulp + browserify (multiple destination) example

gulp + browserify + multiple destination example

Gulp task example using browserify with glob pattern source and multiple destination files.

Bonus features:

• babelify
• exorcist (to externalize the sourcemap)

gulp-browserify-example's Issues

An in-range update of es6-promise is breaking the build 🚨

Version 4.2.0 of es6-promise was just published.

Branch	Build failing 🚨
Dependency	es6-promise
Current Version	4.1.1
Type	devDependency

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

es6-promise 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 18 commits.

• b87f240 release v4.2.0 🎉
• 2faa619 Merge pull request #312 from stefanpenner/remove-dist
• aed7aed [fixes #231]
• 915dc5d Update README.md
• 110dc75 restore minified files to repo (really need to start publishing these
• 64493b6 Merge pull request #289 from stefanpenner/cleanup
• 9d97fb8 cleanup
• d8f56ac Merge pull request #233 from stefanpenner/promise.finally
• 14ca840 Promise.prototype.finally [fixes #232]
• 18897d3 Merge pull request #310 from stefanpenner/updates
• 8f96141 updates
• 44298db Merge pull request #304 from Lcfvs/patch-1
• 08a8a4d Bump ember-cli dep
• e1bb7b6 Merge pull request #306 from LukasDrgon/patch-1
• 4f078b2 Add CDN links

There are 18 commits in total.

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 browserify is breaking the build 🚨

Version 16.2.2 of browserify was just published.

Branch	Build failing 🚨
Dependency	browserify
Current Version	16.2.1
Type	devDependency

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

browserify 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).

---

Release Notes

v16.2.2

Remove some extraneous files from the published package.

Commits

The new version differs by 1 commits.

• fc30e50 16.2.2

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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

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 🌴