unional / aurelia-logging-memory Goto Github PK
View Code? Open in Web Editor NEWMemory appender for aurelia-logging
License: MIT License
Memory appender for aurelia-logging
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 🌴
4.20.2
to 4.21.0
.This version is covered by your current version range and after updating it in your project the build failed.
webpack 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.
output.libraryTarget: "amd-require"
which generates a AMD require([], ...)
wrapper instead of a define([], ...)
wrapperoutput.library
, which exposes the library to a subproperty__webpack_require__.e
is used at runtime but is not defined in the bundleglobal
typeThe new version differs by 37 commits.
432d2a3
4.21.0
0fb6c60
Merge pull request #7038 from marcusdarmstrong/marcusdarmstrong-external-module-fix
15b6f8b
make afterEach async
7bc5c98
Merge branch 'master' into marcusdarmstrong-external-module-fix
2228daf
Merge pull request #8230 from webpack/revert-8120-rh-silent-reporter
fadf875
remove dependency
7c0b209
Revert "Re-enable jest-silent-reporter #hacktoberfest"
a868789
Merge pull request #8143 from MLoughry/miclo/optimize-chunk-graph-generation
1d71ede
Make changes suggested by @sokra to optimize chunk graph generation
4d3fe00
Merge pull request #8134 from fscherwi/update-coveralls
86f56bf
update coveralls
4c461e2
Merge pull request #8120 from rickhanlonii/rh-silent-reporter
9fe42e7
Merge pull request #8118 from webpack/bugfix/issue-8110
0b6ad2a
Don't be clever with the set command because idk windows
148016e
Rerun yarn
There are 37 commits in total.
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 🌴
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 📦🚀
4.28.4
to 4.29.0
.This version is covered by your current version range and after updating it in your project the build failed.
webpack 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.
output.futureEmitAssets
which gives the emitting logic of webpack 5
The new version differs by 10 commits.
25bccd4
4.29.0
6389e41
Merge pull request #8642 from webpack/memory/future-emit-assets
6e383cf
make test for Source.buffer more strict
aaf85db
add output.futureEmitAssets
03ffa48
Merge pull request #8639 from webpack/memory/limit-parallelism
2b2c17f
Merge pull request #8598 from kiliancs/acorn6
80514cc
Add ts declarations
78abf04
Use eachLimit instead even though forEachLimit apears to be an alias...
9cb4225
forEach to forEachLimit
ef67132
Upgrade acorn to v6
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 🌴
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 to 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 📦🚀
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 📦🚀
Branch | Build failing 🚨 |
---|---|
Dependency | tslint |
Current Version | 5.3.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As tslint 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 💪
--type-check
CLI option now only enables checking for compiler errors before linting. It is no longer required to enable rules that use the type checker -- only need to supply --project
now.switch-final-break
(#2804)use-default-type-parameter
(#2253)binary-expression-operand-order
(#2805)ban
new options format: allows to specify an optional explanation message for function bans, banning nested methods and using a wildcard for object of a method ban (#2547)no-duplicate-variable
adds check-parameters
option to check if variable has the same name as a parameter (#2597)curly
: "as-needed" option (#2842)no-unbound-method
add option "ignore-static"
(#2751)strict-boolean-expressions
adds allow-boolean-or-undefined
(#2820)object-literal-shorthand
can fix longhand methods (#2558)prefer-object-spread
allows constructor, function and method calls and more as first argument to Object.assign
(#2828)no-unbound-method
walker skips past the parent if it is a cast or parenthesized expression (#2838)object-literal-shorthand
: fixed suggestion for generator functions (#2558)no-unused-variable
rule on Windows (#2819)tslint --project
if allowJs
is set in tsconfig.json (#2823)align
with option "members"
: check members of class expressions; don't check semicolons in classes (#2668)no-inferred-empty-object-type
: fix stack overflow (#2762)semicolon
: don't warn about unnecesary semicolon when it is actually needed, e.g. when followed by type assertion or template string (#2655)space-before-function-paren
: Ignore async arrow function with no parentheses (#2833)no-unsafe-any
: Don't fail on continue label;
(#2830)no-unbound-method
: Allow unbound method to be used as a condition (#2834)no-unsafe-any
: Allow to switch on a value of type any
(#2836)no-unsafe-any
: Don't mark declare global {}
as an unsafe any. (#2839)indent
now checks indentation of expressions inside template strings (#2826)--project
(or -p
) enables rules that require the type checker. --type-check
only checks for errors before linting is no longer required (#2773)deprecation
: error message includes deprecation text if available (#2748)cyclomatic-complexity
: Don't count empty switch case(#2743)strict-boolean-expressions
: Allow any
, and true
and false
literal types (#2758)no-floating-promises
: Allow 'promise.catch()' (#2774)comment-format
no longer excludes comments with triple slash from linting except /// <reference path="..."/>
(#2616)prefer-object-spread
: lint more locations where return value is used. (#2828)semicolon
: option "never"
is now spec compliant (#2655)object-literal-shorthand
handles async functions correctly (#2558)--test
CLI option: allow passing path to tslint.json (#2784)strict-type-predicates
: warn if strictNullChecks is not enabled (#2786)Thanks to our contributors!
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper 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.