danielbayerlein / honeycomb Goto Github PK
View Code? Open in Web Editor NEWπ Honeycomb is a common basis for @nodejs microservices
License: MIT License
π Honeycomb is a common basis for @nodejs microservices
License: MIT License
it would be great to have controller, which are only accessable via a specific scope.
example: info, status, health should only accessable from admins.
keywords: oauth, jwt, ...
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 π΄
When the project is stable and no longer WIP, we should create an examples folder for react-, handlebars- and further microservices/templates.
We should also create a npm-script for creating/updating this examples. (maybe automatic on new release or commit?)
Branch | Build failing π¨ |
---|---|
Dependency | lerna |
Current Version | 2.0.0-beta.35 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As lerna 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 πͺ
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
Create the honeycomb-layout for tailor
the honeycomb-generator needs some styling for its react-components
Replace the server at honeycomb-assets
of hapi.js
with honeycomb-server
.
We need a solution for handle libraries, that are used by more than 1 honeycomb-template.
example:
maybe we find a better/cleaner solution
Branch | Build failing π¨ |
---|---|
Dependency | lerna |
Current Version | 2.0.0-beta.37 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As lerna 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 πͺ
π¦ π Initial Yarn support and more!
We'll make yarn the default once we feel that it's more stable.
$ lerna bootstrap --npm-client=yarn
{ "npmClient": "yarn" }
This will run yarn
in each package can create temp yarn.lock
files while developing so you'll want to .gitignore/.npmignore
these files. Ex: .gitignore
: packages/*/yarn.lock
Very important fix for Babel that we used in the last release. This prevents a timing issue when publishing where a module will try to download a package that isn't published yet because it is published before it's own dependency is published itself. We used to get many issues from users on non-public npm about "babel-types" not being found.
Useful to get output for child processes immediately if using lerna run
with a watch command
$ lerna run watch --stream
#620 Feature: skip-temp-tag. (@noherczeg)
This will not create a temporary dist-tag called lerna-temp
when publishing. Useful if your third party proxy doesn't support dist-tags.
$ lerna publish --skip-temp-tag
Defaults to running npm run test
and npm run env
{ "commands": { "bootstrap": { "includeFilteredDependencies": true } } }
{ "commands": { "run": { "sort": false } } }
$ lerna publish --registry https://my-private-registry
lerna diff
. (@evocateur)sync-exec
(@wtgtybhertgeghgtwtg)The new version differs by 18 commits .
7202ecc
2.0.0-beta.38
163e22b
Add support for pluggable npm clients (#605)
62a8f2a
Support --skip-temp-tag when publishing (#620)
2f3b195
Add a --stream option to the run command (#608)
3ace547
Add versions to lerna ls. Fixes #603. (#624)
b595884
On import, infer targetDir base from packages glob list (#480)
d246667
lerna publish
checks for changes since most recent tag in the current branch (#475)
744d036
README grammar: it's β its (#609) [skip ci]
5a4039a
Always run test and env scripts (#587)
d7c1fe9
Durable includeFilteredDependencies
config via lerna.json (#598)
3021dc3
Support sort
option in lerna.json (#596)
2e67ed2
Fix midair collision (#604)
6b5fb91
Explicit registry flag feature (#599)
8790656
Publish npm packages in topological order. (#595)
925c0a1
Fix --ignore flag when globs are expanded to an array (#601)
There are 18 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
the generated services with generator-honeycomb should have 100% coverage
we should extract the logger (+config) in a honeycomb-package.
We should also include the logger-package into honeycomb-layout.
it would be good, to test the layout-components
2.0.5
to 2.0.6
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
yo 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 π΄
the honeycomb-generator needs some styling for its handlebars-template.
Branch | Build failing π¨ |
---|---|
Dependency | husky |
Current Version | 0.13.2 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As husky 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 9 commits .
4b5011e
0.13.3
6b92bb8
Comments
c6f8bb1
0.13.3-0
a2da709
Prefer nvm over Node global install
652c7f0
Update README.md
d05a7b3
Update README.md
0bb5798
Fix tests
7af95d3
update failure message (#107)
be435ca
Update CHANGELOG.md
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 | lerna |
Current Version | 2.0.0-beta.34 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As lerna 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 πͺ
3 new flags:
--no-sort
(only for run, exec and bootstrap)By default, all tasks execute on packages in topologically sorted order as to respect the dependency relationships of the packages in question. Cycles are broken on a best-effort basis in a way not guaranteed to be consistent across Lerna invocations.
Topological sorting can cause concurrency bottlenecks if there are a small number of packages with many dependents or if some packages take a disproportionately long time to execute. The --no-sort
option disables sorting, instead executing tasks in an arbitrary order with maximum concurrency.
--hoist
(only for bootstrap)Install external dependencies matching glob
at the repo root so they're
available to all packages. Any binaries from these dependencies will be
linked into dependent package node_modules/.bin/
directories so they're
available for npm scripts. If the option is present but no glob
is given
the default is **
(hoist everything). This option only affects the
bootstrap
command.
$ lerna bootstrap --hoist
Note: If packages depend on different versions of an external dependency,
the most commonly used version will be hoisted, and a warning will be emitted.
This option may also be set in lerna.json
with "hoist": true
or "hoist": <glob>
.
--nohoist
(only for bootstrap)Do not install external dependencies matching glob
at the repo root. This
can be used to opt out of hoisting for certain dependencies.
$ lerna bootstrap --hoist --nohoist=babel-*
This option may also be set in lerna.json
with "nohoist": <glob>
.
lerna clean
). (@roblg)--include-filtered-dependencies
flag. (@roblg)--scope --include-filtered-dependencies
. (@roblg)When running lerna bootstrap --scope foo --include-filtered-dependencies
run prepublish task with the same flags.
cross-env
.. (@wtgtybhertgeghgtwtg)isarray
.. (@wtgtybhertgeghgtwtg)signal-exit
.. (@wtgtybhertgeghgtwtg)object-assigned-sorted
.. (@wtgtybhertgeghgtwtg)object-assign
.. (@wtgtybhertgeghgtwtg)inquirer
dependency. (@wtgtybhertgeghgtwtg)The new version differs by 48 commits .
e3fc0e9
2.0.0-beta.35
05ceaaa
fix version [skip ci]
b35c05f
update changelog [skip ci] (#561)
77b77fa
Bump cross-env
. (#554)
560348c
Updating README: clean
respects --include-filtered-dependencies (#558) [skip ci]
5996375
redo labels [skip ci] (#560)
4b6f0aa
Drop isarray
. (#559)
bcaf1aa
Fix broken hoisting tests (#557)
6e9bf13
Merge pull request #507 from gigabo/hoist
0b016de
Spawn child process for rimraf (#547)
bc93b96
Bump signal-exit
. (#549)
84b81ab
Use real Object.assign now that we're off of 0.10/0.12
3a61c69
Don't prune the repo root when hoisting (#67)
4eaf88e
Kill some duplicate methods
f7b8b3e
Automatic hoisting of common dependencies to repo root (#36)
There are 48 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
it looks like that we will need an amd-bundler/loader for honeycomb-layout.
currently there will be an error, because react is undefined in example-react.
if i understand the examples for tailor right, we should use require.js to handle this case.
we should extract the logic for health and info-controller into a sperate package.
like https://github.com/ziyasal/hapijs-status-monitor
Our test files do not have a uniform name:
eslint-config-honeycomb
-> *-test.js
generator-honeycomb
-> *-test.js
honeycomb-assets
-> *.test.js
honeycomb-health-middleware
-> *.js
honeycomb-info-middleware
-> *.js
honeycomb-layout
-> *-test.js
honeycomb-logging-middleware
-> *.js
honeycomb-registry-client
-> *-test.js
honeycomb-server
-> *.js
@chrishelgert Do you prefer *-test.js
or *.test.js
?
I think it makes sense if we create a linter package.
Support
Maybe one package is enough, see https://github.com/sindresorhus/eslint-config-xo.
I think it makes sense to create a honeycomb-server
package with hapi.js
.
I think it would be great to use styled-components with Preact again.
Reading matter:
2.6.2
to 2.6.3
.π¨ View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
rimraf 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 6 commits.
9442819
2.6.3
42fe369
autopublish scripts
21fd3df
bin test
8f1d3a1
update tap and glob for security stuff
f0bc3a1
update tap, add package-lock
692022b
travis node version updates
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 | lerna |
Current Version | 2.0.0-beta.36 |
Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As lerna 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 πͺ
--include-filtered-dependencies
now works with ls
,exec
,run
as well!
--hoist
(from previous release)lodash.find
, lodash.unionwith
, and pad
with lodash
.. (@wtgtybhertgeghgtwtg)command-join
.. (@wtgtybhertgeghgtwtg)The new version differs by 17 commits .
bf16868
2.0.0-beta.37
e95921a
remove .only test
a88178d
fixes [skip ci]
9b79932
v2.0.0-beta.37 changelog [skip ci]
ceed21c
Replace lodash.find
, lodash.unionwith
, and pad
with lodash
. (#562)
a3472d7
Bump command-join
. (#584)
d1ec2e1
v2.0.0-beta.36 changelog [skip ci]
eb02684
Improves support for --include-filtered-dependencies (#581)
3e7637e
Merge pull request #576 from gigabo/naked-install
0516be7
Merge pull request #575 from doug-wade/add-nyc
793f906
Add tests for FileSystemUtilities.rename*
406015b
Add tests for NpmUtilities.splitVersion
a87c76c
Use correct logger method in Package method. (#574)
4d3a6f5
Install with no arguments
b6618f2
Add coverage report
There are 17 commits in total. See the full diff.
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot π΄
we should deliver the assets (asset-service, generator-honeycomb) with gzip when possible.
https://github.com/webpack/compression-webpack-plugin
new CompressionPlugin({
asset: "[path].gz[query]",
algorithm: "gzip",
test: /\.js$|\.css$|\.html$/,
threshold: 10240,
minRatio: 0.8
});
found a example only for express
app.get('*.js', (req, res) => {
req.url = req.url + '.gz';
req.set('Content-Encoding', 'gzip');
next();
});
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.