Giter VIP home page Giter VIP logo

honeycomb's Introduction

Hi, I'm Daniel πŸ‘‹

GitHub Stats

Daniel Bayerlein's DEV Profile  

honeycomb's People

Contributors

chrishelgert avatar danielbayerlein avatar greenkeeper[bot] avatar hablijack avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

honeycomb's Issues

[generator-honeycomb] Scoped controller

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, ...

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 🌴

Create examples

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?)

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

Version 2.0.0-beta.36 of lerna just got published.

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 πŸ’ͺ


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 2 commits .

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 🌴

Styling for react-template

the honeycomb-generator needs some styling for its react-components

  • postcss / scss / aphrodite / radium
  • autoprefixer
  • extend unit-tests for new generator-cases

Handle global libraries

We need a solution for handle libraries, that are used by more than 1 honeycomb-template.

example:

  • react, react-dom will be served with honeycomb-asset
  • react, react-dom are externals in honeycomb-template (webpack.config, maybe only in production)

maybe we find a better/cleaner solution

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

Version 2.0.0-beta.38 of lerna just got published.

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 πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes v2.0.0-beta.38

v2.0.0-beta.38 (2017-02-28)

πŸ“¦ 🐈 Initial Yarn support and more!

πŸš€ Enhancement

  • #605 Add support for pluggable npm clients. (@gigabo)

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.

  • #608 Add a --stream option to the run command. (@gigabo)

Useful to get output for child processes immediately if using lerna run with a watch command

$ lerna run watch --stream

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

  • #598 Durable includeFilteredDependencies config via lerna.json. (@gigabo)
{
  "commands": {
    "bootstrap": {
      "includeFilteredDependencies": true
    }
  }
}
{
  "commands": {
    "run": {
      "sort": false
    }
  }
}
$ lerna publish --registry https://my-private-registry

πŸ› Bug Fix

  • #601 Fix --ignore flag when globs are expanded to an array. (@rtsao)
  • #597 Support command config in either "commands" or "command". (@gigabo)
  • #586 Avoid exception after successful lerna diff. (@evocateur)

🏠 Internal

Committers: 11

Commits

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.

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 🌴

Extract logger in honeycomb-package

we should extract the logger (+config) in a honeycomb-package.

  • middleware
  • logger

We should also include the logger-package into honeycomb-layout.

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

The devDependency yo was updated from 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.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 2 commits.

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 🌴

Styling for handlebars-template

the honeycomb-generator needs some styling for its handlebars-template.

  • postcss or scss
  • autoprefixer
  • no need for normalizr
  • extend unit-tests for new generator-cases

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

Version 0.13.3 of husky just got published.

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 πŸ’ͺ


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 9 commits .

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

Version 2.0.0-beta.35 of lerna just got published.

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 πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes v2.0.0-beta.35

v2.0.0-beta.35 (2017-02-01)

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

πŸš€ Enhancement

  • #507 Automatic hoisting of common dependencies. (@gigabo)
  • #547 Spawn child process for rimraf (speeds up lerna clean). (@roblg)
  • #543 [clean] Support --include-filtered-dependencies flag. (@roblg)
  • #412 Make bootstrap, exec and run commands execute packages in dependency order by default. (@seansfkelley)
  • #373 [Feature] Log stdout when commands fail. Closes #343.. (@seansfkelley)

πŸ› Bug Fix

  • #542 Fixes issue: prepublish not running in dependencies with --scope --include-filtered-dependencies. (@roblg)

When running lerna bootstrap --scope foo --include-filtered-dependencies run prepublish task with the same flags.

πŸ“ Documentation

🏠 Internal

Committers: 9

Commits

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.

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 🌴

[honeycomb-layout] Use AMD

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.

Naming convention for test files

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?

honeycomb-server

I think it makes sense to create a honeycomb-server package with hapi.js.

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

The devDependency rimraf was updated from 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.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 6 commits.

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

Version 2.0.0-beta.37 of lerna just got published.

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 πŸ’ͺ


Status Details
  • ❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Release Notes v2.0.0-beta.37

v2.0.0-beta.37 (2017-02-08)

--include-filtered-dependencies now works with ls,exec,run as well!

  • Fixes an issue with --hoist (from previous release)

πŸš€ Enhancement

  • #581 Improve support for --include-filtered-dependencies. (@roblg)
  • #576 Install with no arguments. (@gigabo)
  • #569 Short-circuit out of install with no packages. (@gigabo)

πŸ› Bug Fix

  • #574 Use correct logger method in Package method.. (@evocateur)
  • #568 Check if directories exist before removing during hoist. (@gigabo)

🏠 Internal

Committers: 5

Commits

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.

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 🌴

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.