unional / global-test-harness Goto Github PK
View Code? Open in Web Editor NEWCreate test harness to test global namespace codes like module codes
License: MIT License
Create test harness to test global namespace codes like module codes
License: MIT License
To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:
.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.
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 🤖
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
master
branch failed. 🚨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project ✨
Your semantic-release bot 📦🚀
1.0.3
to 1.0.4
.This version is covered by your current version range and after updating it in your project the build failed.
aurelia-logging-color 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 | nyc |
Current Version | 11.2.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
nyc 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.
The new version differs by 12 commits.
d85118c
chore(release): 11.3.0
7792733
chore: explicitly update istanbul dependencies (#698)
222a3d0
chore: slight difference in pinning logic, based on @ljharb's advice
f04b7a9
feat: add option to hook vm.runInContext (#680)
cdfdff3
feat: add --exclude-after-remap option for users who pre-instrument their codebase (#697)
a413f6a
chore: upgrade to yargs 10 (#694)
10125aa
docs: fix reporters link
f5089ca
docs: added examples of coverage reports (#656)
af281e7
chore: update spawn-wrap to 1.4.0 (#692)
a685f7c
docs: missing options prefix -- in front of check-coverage (#695)
f31d7a6
feat: allow instrument-only to produce sourcemaps (#674)
425c0fd
chore: ignore package-lock.json (#683)
See the full diff
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 | source-map-loader |
Current Version | 0.2.1 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As source-map-loader 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 💪
The new version differs by 5 commits.
fdcfea6
chore(release): 0.2.2
38da2eb
fix: Handle exception on loading invalid base64 source maps (#53)
e0bff76
docs(README): define more precisely what loader does (#47)
54ee6ea
Remove plus signs from copy. (#44)
5501fe3
docs(README): add details on usage and purpose (#37)
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 | aurelia-logging-color |
Current Version | 0.5.5 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
aurelia-logging-color 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.
The new version differs by 7 commits.
f4183cd
0.5.6
fa57490
Remove lint --type-check
c7e4cb2
Update deps (#10)
1f67efd
chore(package): update ava to version 0.23.0 (#9)
899561f
Update .travis.yml
034e0a8
Update dependencies to enable Greenkeeper 🌴 (#8)
4d535dd
Rename foreground back to color (#7)
See the full diff
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 | eslint |
Current Version | 4.7.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As eslint 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 💪
The new version differs by 14 commits.
8ebb034
4.8.0
916a2d7
Build: changelog update for 4.8.0
3f2b908
New: add option to report unused eslint-disable directives (fixes #9249) (#9250)
ff2be59
Fix: dot notation rule failing to catch string template (fixes #9350) (#9357)
b1372da
Chore: remove sourceCode property from Linter (refs #9161) (#9363)
cef6f8c
Docs: remove line about removing rules from semver policy (#9367)
06efe87
Fix: Add meta element with charset attribute. (#9365)
458ca67
Docs: update architecture page (fixes #9337) (#9345)
1c6bc67
Fix: special EventEmitter keys leak information about other rules (#9328)
d593e61
Docs: update eslint.org links to use https (#9358)
38d0cb2
Fix: fix wrong code-path about try-for-in (fixes #8848) (#9348)
434d9e2
Fix: Invalid font-size property value issue. (#9341)
a7668c2
Chore: Remove unnecessary slice from logging utility (#9343)
2ff6fb6
Chore: remove unused arguments in codebase (#9340)
See the full diff
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
1.4.0
to 1.4.1
.This version is covered by your current version range and after updating it in your project the build failed.
@unional/devpkg-node 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 🌴
1.0.3
to 1.0.4
.This version is covered by your current version range and after updating it in your project the build failed.
@unional/logging is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.
Your Greenkeeper Bot 🌴
master
branch failed. 🚨I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.
You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.
Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.
Once all the errors are resolved, semantic-release will release your package the next time you push a commit the master
branch. You can also manually restart the failed CI job that runs semantic-release.
If you are not sure how to resolve this, here is some links that can help you:
If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.
The npm token configured in the NPM_TOKEN
environment variable must be a valid token allowing to publish to the registry https://registry.npmjs.org/
.
If you are using Two-Factor Authentication, make configure the auth-only
level is supported. semantic-release cannot publish with the default auth-and-writes
level.
Please make sure to set the NPM_TOKEN
environment variable in your CI with the exact value of the npm token.
Good luck with your project ✨
Your semantic-release bot 📦🚀
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 is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
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.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.