unional / komondor-plugin-node Goto Github PK

View Code? Open in Web Editor NEW

0.0 3.0 0.0 823 KB

NodeJS plugin for komondor

License: MIT License

Shell 4.08% JavaScript 8.87% TypeScript 87.06%

komondor-plugin-node's Introduction

komondor-plugin-node

komondor plugin for NodeJS.

It adds support for:

childProcess
stream

To use this plugin, add it to your komondor config in the package.json:

{
  "komondor": {
    "plugins": ["komondor-plugin-node"]
  }
}

Contribute

# right after fork
npm install

# begin making changes
git checkout -b <branch>
npm run watch

# edit `webpack.config.dev.js` to exclude dependencies for the global build.

# after making change(s)
git commit -m "<commit message>"
git push

# create PR

Npm Commands

There are a few useful commands you can use during development.

# Run tests (and lint) automatically whenever you save a file.
npm run watch

# Run tests with coverage stats (but won't fail you if coverage does not meet criteria)
npm run test

# Manually verify the project.
# This will be ran during 'npm preversion' so you normally don't need to run this yourself.
npm run verify

# Build the project.
# You normally don't need to do this.
npm run build

# Run tslint
# You normally don't need to do this as `npm run watch` and `npm version` will automatically run lint for you.
npm run lint

Generated by [email protected]

TODO

work on browser

komondor-plugin-node's People

Contributors

Watchers

komondor-plugin-node's Issues

An in-range update of semantic-release is breaking the build 🚨

The devDependency semantic-release was updated from `15.13.23` to `15.13.24`.

🚨 View failing branch.

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

semantic-release 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 for v15.13.24

15.13.24 (2019-08-22)

Reverts

docs: broken link docs/03-recipes/travis.md (eea5de2)
docs: cleaned "Developer guide" section navigation (3c4a0fb)
docs: corrections and further clarifications (ce3d1bc)
docs: made doc file org clearer and augmented content (5e41dc8)
docs: note publishing on distribution channels in beta (54d8e3f)
docs: repared broken links to "CI configuration recipes" (e00b6c8)
docs: synched README.md and SUMMARY.md (e770c50)
docs: update semantic-release-cli broken link (58aaf05)
docs(contributing): added instructions on how to run gitbook locally (55c3616)
docs(contributing): copy/pasted "Use gitbook locally" instruction from original url (c517c70)
docs(recipes): cleaned doc and navigation (a6188d3)
fix(definitions): Repository documentation links (95a9e89)

Commits

The new version differs by 16 commits.

6f33c76 docs: various clarifications and language improvvements
9fd93ac docs: fix node version requirement link is FAQ
7ddc2cf docs: update table of content in README.md and in Gitbook SUMMARY.md
55c3616 revert: docs(contributing): added instructions on how to run gitbook locally
c517c70 revert: docs(contributing): copy/pasted "Use gitbook locally" instruction from original url
4b13280 docs: correct list of default plugins
95a9e89 revert: fix(definitions): Repository documentation links
54d8e3f revert: docs: note publishing on distribution channels in beta
a6188d3 revert: docs(recipes): cleaned doc and navigation
e00b6c8 revert: docs: repared broken links to "CI configuration recipes"
3c4a0fb revert: docs: cleaned "Developer guide" section navigation
e770c50 revert: docs: synched README.md and SUMMARY.md
5e41dc8 revert: docs: made doc file org clearer and augmented content
ce3d1bc revert: docs: corrections and further clarifications
58aaf05 revert: docs: update semantic-release-cli broken link

There are 16 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 🌴

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 🌴

childProcess is not working

The actual childProcess does not work for some reason. Seems to be function issue, but don't know why.

The automated release is failing 🚨

🚨 The automated release from the `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 push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment.

Good luck with your project ✨

Your semantic-release bot 📦🚀

create a complete fake childProcess

komondor-plugin-node/src/childProcess/index.ts

Lines 50 to 55 in 359ccd3

 const spiedArgs = call.invoke([event, cb]) 

 const result = fn.call(subject, ...spiedArgs) 

 call.return(result) 

 return result 

 } 

 }

This issue was generated by todo based on a `TODO` comment in `359ccd3` when #9 was merged. cc @unional.

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 it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

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

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

support fs

spy and stub onfs

create a complete fake childProcess

komondor-plugin-node/src/childProcess/index.ts

Lines 50 to 55 in 0e81b1a

 const spiedArgs = call.invoke([event, cb]) 

 const result = fn.call(subject, ...spiedArgs) 

 call.return(result) 

 return result 

 } 

 }

This issue was generated by todo based on a `TODO` comment in `0e81b1a`. It's been assigned to @unional because they committed the code.

streamReceivedMultipleData() does not work with spread

s.satisfy([
  ...,
  { ...streamReceivedMultipleData(), ... }
])

This code does not work because satisfier using instanceof comparison.

	const spiedArgs = call.invoke([event, cb])
	const result = fn.call(subject, ...spiedArgs)
	call.return(result)
	return result
	}
	}