build
commented
3 years ago | Warnings | |
|---|---|
| :warning: | **lib/fserver.js#L193** - lib/fserver.js line 193 – 'url.parse' was deprecated since v11.0.0. Use 'url.URL' constructor instead. (node/no-deprecated-api) |
| :warning: | **lib/fserver.js#L244** - lib/fserver.js line 244 – Missing JSDoc @returns for function. (valid-jsdoc) |
| :warning: | **lib/platform/events.js#L12** - lib/platform/events.js line 12 – Import and export declarations are not supported yet. (node/no-unsupported-features/es-syntax) |
| :warning: | **lib/platform/main.js#L5** - lib/platform/main.js line 5 – Import and export declarations are not supported yet. (node/no-unsupported-features/es-syntax) |
| :warning: | **lib/platform/process.js#L1** - lib/platform/process.js line 1 – Import and export declarations are not supported yet. (node/no-unsupported-features/es-syntax) |
| :warning: | **lib/platform/process.js#L8** - lib/platform/process.js line 8 – Import and export declarations are not supported yet. (node/no-unsupported-features/es-syntax) |
| :warning: | **lib/platform/require.js#L1** - lib/platform/require.js line 1 – Import and export declarations are not supported yet. (node/no-unsupported-features/es-syntax) |
| :warning: | **lib/platform/require.js#L9** - lib/platform/require.js line 9 – Import and export declarations are not supported yet. (node/no-unsupported-features/es-syntax) |
| :warning: | **lib/platform/socket.js#L1** - lib/platform/socket.js line 1 – Import and export declarations are not supported yet. (node/no-unsupported-features/es-syntax) |
| Messages | |
|---|---|
| :book: | :white_check_mark: All tests are passing Nice one! All 4 tests are passing. |
New dependencies added: @commitlint/cli, @commitlint/config-conventional, @seadub/danger-plugin-dependencies, @seadub/danger-plugin-eslint, @seadub/danger-plugin-junit, danger, eslint, eslint-config-axway, eslint-plugin-mocha, husky, lint-staged, nyc and rollup.
@seadub/danger-plugin-dependencies
Author: Chris Williams
Description: Provides dependency information on dependency changes in a PR
Homepage: https://github.com/sgtcoolguy/danger-plugin-dependencies#readme
| Created | almost 2 years ago |
| Last Updated | 15 days ago |
| License | MIT |
| Maintainers | 1 |
| Releases | 3 |
| Direct Dependencies | date-fns, lodash.flatten, lodash.includes, node-fetch and semver |
| Keywords | danger, danger-plugin, npm, yarn and dependencies |
README
# danger-plugin-dependencies
[](https://badge.fury.io/js/@seadub/danger-plugin-dependencies)
> Provides dependency information on dependency changes in a PR
## Usage
Install:
```sh
npm install @seadub/danger-plugin-dependencies --save-dev
# or
yarn add @seadub/danger-plugin-dependencies --dev
```
At a glance:
```js
// dangerfile.js
import dependencies from '@seadub/danger-plugin-dependencies'
schedule(dependencies())
```
Provides 4 separate rules:
* `checkForRelease` - Provides a 🎉 when there's a package version bump.
* `checkForNewDependencies` (async) - Provides npmjs.com (and `yarn why`, when type is `"yarn"`) metadata about new dependencies.
* `checkForLockfileDiff` - Will warn you when there are `dependencies` or `devDependencies` changes without a `package-lock.json` or `yarn.lock` change.
* `checkForTypesInDeps` - Will fail the build if you add any `@types/[x]` to `dependencies` instead of `devDependencies`.
And exports a default function to handle all of them at once.
Note: async functions like the default one [have be to](http://danger.systems/js/guides/the_dangerfile.html#async) `schedule`'d by Danger.
## `yarn` vs `npm` usage
By default, the `dependencies` method will attempt to determine if you are using `npm` or `yarn` to manage your dependencies based on sniffing for the lockfiles on disk. If no lockfiles exist, or running on Peril it will fail without an explicitly stated manasger type in the options.
You may explicitly pass one in the options:
```js
// dangerfile.js
import dependencies from '@seadub/danger-plugin-dependencies'
schedule(dependencies({ type: "npm" }))
// or for yarn
schedule(dependencies({ type: "yarn" }))
```
## Private packages
If you want the plugin to find your private packages on npm, you need to provide an npm [authentication token](https://docs.npmjs.com/getting-started/working_with_tokens):
```js
// dangerfile.js
import dependencies from 'danger-plugin-dependencies'
schedule(dependencies({ npmAuthToken: 'xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx' }))
```
## Changelog
See the GitHub [release history](https://github.com/sgtcoolguy/danger-plugin-dependencies/releases).
## Contributing
See [CONTRIBUTING.md](contributing.md).
## What does this look like?
The rest of this README is the contents of what it looks like when you add this plugin to your Dangerfile:
---
| Warnings | |
|---|---|
| :warning: | New dependencies added: danger-plugin-yarn. |
danger-plugin-yarn
Author: Orta Therox
Description: Provides dependency information on dependency changes in a PR
Homepage: https://github.com/orta/danger-plugin-yarn#readme
| Created | 24 days ago |
| Last Updated | 3 minutes ago |
| License | MIT |
| Maintainers | 1 |
| Releases | 14 |
| Direct Dependencies | date-fns, lodash.flatten, lodash.includes, node-fetch and esdoc |
| Keywords | danger, danger-plugin and yarn |
README
# danger-plugin-yarn
[](https://travis-ci.org/orta/danger-plugin-yarn)
[](https://badge.fury.io/js/danger-plugin-yarn)
[](https://github.com/semantic-release/semantic-release)
> Provides dependency information on dependency changes in a PR
## Usage
Install:
```sh
yarn add danger-plugin-yarn --dev
```
At a glance:
```js
// dangerfile.js
import yarn from 'danger-plugin-yarn'
schedule(yarn())
```
Provides 4 separate rules:
* `checkForRelease` - Provides a 🎉 when there's a package version bump.
* `checkForNewDependencies` (async) - Provides npmjs.com and `yarn why` metadata about new dependencies.
* `checkForLockfileDiff` - Will warn you when there are `dependencies` or `devDependencies` changes without a `yarn.lock` change.
* `checkForTypesInDeps` - Will fail the build if you add any `@types/[x]` to `dependencies` instead of `devDependencies`.
And exports a default function to handle all of them at once.
Note: async functions like the default one [have be to](http://danger.systems/js/guides/the_dangerfile.html#async) `schedule`'d by Danger.
## Changelog
See the GitHub [release history](https://github.com/orta/danger-plugin-yarn/releases).
## Contributing
See [CONTRIBUTING.md](contributing.md).
yarn why danger-plugin-yarn output
Generated by :no_entry_sign: dangerJS
@seadub/danger-plugin-eslint
Author: Chris Williams
Description: Eslint your code with Danger
Homepage: https://github.com/sgtcoolguy/danger-plugin-eslint#readme
| Created | almost 2 years ago |
| Last Updated | 3 months ago |
| License | MIT |
| Maintainers | 1 |
| Releases | 5 |
| Direct Dependencies | |
| Keywords | danger, danger-plugin and eslint |
README
# danger-plugin-eslint
[](https://travis-ci.org/danpalmer/danger-plugin-eslint)
[](https://badge.fury.io/js/danger-plugin-eslint)
[](https://github.com/semantic-release/semantic-release)
> Eslint your code with Danger
## Usage
Install:
```sh
yarn add danger-plugin-eslint --dev
```
At a glance:
```js
// dangerfile.js
import eslint from 'danger-plugin-eslint'
eslint()
```
## Changelog
See the GitHub [release history](https://github.com/danpalmer/danger-plugin-eslint/releases).
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md).
@seadub/danger-plugin-junit
Author: Christopher Williams
Description: Add your Junit XML test failures to Danger
Homepage: https://github.com/sgtcoolguy/danger-plugin-junit#readme
| Created | almost 2 years ago |
| Last Updated | 3 months ago |
| License | MIT |
| Maintainers | 1 |
| Releases | 6 |
| Direct Dependencies | fs-extra, glob and xmldom |
| Keywords | danger, danger-plugin and junit |
README
# danger-plugin-junit
[](https://travis-ci.org/sgtcoolguy/danger-plugin-junit)
[](https://badge.fury.io/js/danger-plugin-junit)
> Add your Junit XML test failures to Danger
## Usage
Install:
```sh
npm install danger-plugin-junit --save-dev
# or
yarn add danger-plugin-junit --dev
```
At a glance:
```js
// dangerfile.js
import junit from 'danger-plugin-junit'
async function main() {
await junit({ pathToReport: './build/reports/**/TESTS*.xml' })
}
main()
.then(() => process.exit(0))
.catch(err => {
fail(err.toString());
process.exit(1);
});
```
The default `pathToReport` value is `'./build/reports/**/TESTS*.xml'`
The value is a [glob](https://www.npmjs.com/package/glob) string to gather up test result files.
This plugin will only report test failures and errors. If any tests fail, it will report a single `fail()` message and record a table of the failed tests using `markdown()`.
An example of what is produced is below:
## Changelog
See the GitHub [release history](https://github.com/sgtcoolguy/danger-plugin-junit/releases).
## Contributing
See [CONTRIBUTING.md](CONTRIBUTING.md).
danger
Author: Orta Therox
Description: Unit tests for Team Culture
Homepage: https://github.com/danger/danger-js#readme
| Created | over 4 years ago |
| Last Updated | 20 days ago |
| License | MIT |
| Maintainers | 3 |
| Releases | 277 |
| Direct Dependencies | @babel/polyfill, @octokit/rest, async-retry, chalk, commander, debug, fast-json-patch, get-stdin, gitlab, http-proxy-agent, https-proxy-agent, hyperlinker, json5, jsonpointer, jsonwebtoken, lodash.find, lodash.includes, lodash.isobject, lodash.keys, lodash.mapvalues, lodash.memoize, memfs-or-file-map-to-github-branch, micromatch, node-cleanup, node-fetch, override-require, p-limit, parse-diff, parse-git-config, parse-github-url, parse-link-header, pinpoint, prettyjson, readline-sync, require-from-string and supports-hyperlinks |
| Keywords | danger and ci |
README
Formalize your Pull Request etiquette.
What is Danger JS? • Vision • Helping Out • Plugin Development
## What is Danger JS? Danger runs after your CI, automating your team's conventions surrounding code review. This provides another logical step in your process, through which Danger can help lint your rote tasks in daily code review. You can use Danger to codify your team's norms, leaving humans to think about harder problems. Danger JS works with GitHub, BitBucket Server, BitBucket Cloud for code review, then with: Travis CI, GitLab CI, Semaphore, Circle CI, GitHub Actions, Jenkins, Docker Cloud, Bamboo, Bitrise, surf-build, Codeship, Drone, Buildkite, Nevercode, buddybuild, Buddy.works, TeamCity, Visual Studio Team Services, Screwdriver, Concourse, Netlify, CodeBuild, Codefresh, AppCenter, BitBucket Pipelines, or Cirrus CI. [](https://www.npmjs.com/package/danger) [](https://travis-ci.org/danger/danger-js) [](https://ci.appveyor.com/project/orta/danger-js/branch/master) [](https://spectrum.chat/danger) ## For example? You can: - Enforce CHANGELOGs - Enforce links to Trello/JIRA in PR/MR bodies - Enforce using descriptive labels - Look out for common anti-patterns - Highlight interesting build artifacts - Give warnings when specific files change Danger provides the glue to let _you_ build out the rules specific to your team's culture, offering useful metadata and a comprehensive plugin system to share common issues. ## Getting Started Alright. So, actually, you may be in the wrong place. From here on in, this README is going to be for people who are interested in working on and improving on Danger JS. We keep all of the end-user documentation at@commitlint/config-conventional
Author: Mario Nebl
Description: Shareable commitlint config enforcing conventional commits
Homepage: https://github.com/conventional-changelog/commitlint#readme
| Created | almost 3 years ago |
| Last Updated | about 1 month ago |
| License | MIT |
| Maintainers | 4 |
| Releases | 34 |
| Direct Dependencies | conventional-changelog-conventionalcommits |
| Keywords | conventional-changelog, commitlint, commitlint-config and angular |
eslint-config-axway
Author: Axway, Inc.
Description: Shareable eslint config for Axway projects
Homepage: https://github.com/appcelerator/eslint-config-axway#readme
| Created | over 3 years ago |
| Last Updated | 11 days ago |
| License | Apache-2.0 |
| Maintainers | 3 |
| Releases | 42 |
| Direct Dependencies | eslint-plugin-chai-expect, eslint-plugin-import, eslint-plugin-node, eslint-plugin-promise, eslint-plugin-security, find-root and semver |
| Keywords | appcelerator, axway, config, eslint, eslintconfig, eslint-config, javascript, jscs, jshint, lint, linter, linting and styleguide |
This README is too long to show.
eslint-plugin-mocha
Author: Mathias Schreck
Description: Eslint rules for mocha.
Homepage: https://github.com/lo1tuma/eslint-plugin-mocha
| Created | about 6 years ago |
| Last Updated | 3 months ago |
| License | MIT |
| Maintainers | 3 |
| Releases | 46 |
| Direct Dependencies | eslint-utils and ramda |
| Keywords | eslint, eslintplugin, eslint-plugin and mocha |
README
[](https://www.npmjs.org/package/eslint-plugin-mocha)
[](https://github.com/lo1tuma/eslint-plugin-mocha/actions)
[](https://coveralls.io/r/lo1tuma/eslint-plugin-mocha)
[](https://david-dm.org/lo1tuma/eslint-plugin-mocha#info=peerDependencies&view=table)
[](https://www.npmjs.org/package/eslint-plugin-mocha)
# eslint-plugin-mocha
ESLint rules for [mocha](http://mochajs.org/).
## Install and configure
This plugin requires ESLint `4.0.0` or later.
```bash
npm install --save-dev eslint-plugin-mocha
```
Then add a reference to this plugin and selected rules in your eslint config:
```json
{
"plugins": [
"mocha"
]
}
```
### Plugin Settings
This plugin supports the following settings, which are used by multiple rules:
* `additionalCustomNames`: This allows rules to check additional function names when looking for suites or test cases. This might be used with a custom Mocha extension, such as [`ember-mocha`](https://github.com/switchfly/ember-mocha)
**Example:**
```json
{
"rules": {
"mocha/no-skipped-tests": "error",
"mocha/no-exclusive-tests": "error"
},
"settings": {
"mocha/additionalCustomNames": [
{ "name": "describeModule", "type": "suite", "interfaces": [ "BDD" ] },
{ "name": "testModule", "type": "testCase", "interfaces": [ "TDD" ] }
]
}
}
```
### Recommended config
This plugin exports a recommended config that enforces good practices.
Enable it with the extends option:
```json
{
"extends": [
"plugin:mocha/recommended"
]
}
```
See [Configuring Eslint](http://eslint.org/docs/user-guide/configuring) on [eslint.org](http://eslint.org) for more info.
## Rules documentation
The documentation of the rules [can be found here](docs/rules).
husky
Author: Typicode
Description: Prevents bad commit or push (git hooks, pre-commit/precommit, pre-push/prepush, post-merge/postmerge and all that stuff...)
Homepage: https://github.com/typicode/husky#readme
| Created | over 6 years ago |
| Last Updated | 5 days ago |
| License | MIT |
| Maintainers | 1 |
| Releases | 163 |
| Direct Dependencies | chalk, ci-info, compare-versions, cosmiconfig, find-versions, opencollective-postinstall, pkg-dir, please-upgrade-node, slash and which-pm-runs |
| Keywords | git, hook, hooks, pre-commit, precommit, post-commit, postcommit, pre-push, prepush, post-merge, postmerge, test and lint |
lint-staged
Author: Andrey Okonetchnikov
Description: Lint files staged by git
Homepage: https://github.com/okonet/lint-staged#readme
| Created | almost 5 years ago |
| Last Updated | 4 days ago |
| License | MIT |
| Maintainers | 1 |
| Releases | 168 |
| Direct Dependencies | chalk, cli-truncate, commander, cosmiconfig, debug, dedent, enquirer, execa, listr2, log-symbols, micromatch, normalize-path, please-upgrade-node, string-argv and stringify-object |
| Keywords | lint, git, staged, eslint, prettier, stylelint, code, quality, check, format and validate |
This README is too long to show.
nyc
Author: Ben Coe
Description: the Istanbul command line interface
Homepage: https://istanbul.js.org/
| Created | over 5 years ago |
| Last Updated | 5 months ago |
| License | ISC |
| Maintainers | 3 |
| Releases | 163 |
| Direct Dependencies | @istanbuljs/load-nyc-config, @istanbuljs/schema, caching-transform, convert-source-map, decamelize, find-cache-dir, find-up, foreground-child, get-package-type, glob, istanbul-lib-coverage, istanbul-lib-hook, istanbul-lib-instrument, istanbul-lib-processinfo, istanbul-lib-report, istanbul-lib-source-maps, istanbul-reports, make-dir, node-preload, p-map, process-on-spawn, resolve-from, rimraf, signal-exit, spawn-wrap, test-exclude and yargs |
| Keywords | coverage, reporter, subprocess and testing |
This README is too long to show.
@commitlint/cli
Author: Mario Nebl
Description: Lint your commit messages
Homepage: https://github.com/conventional-changelog/commitlint#readme
| Created | over 3 years ago |
| Last Updated | about 1 month ago |
| License | MIT |
| Maintainers | 4 |
| Releases | 67 |
| Direct Dependencies | @babel/runtime, @commitlint/format, @commitlint/lint, @commitlint/load, @commitlint/read, chalk, core-js, get-stdin, lodash, resolve-from, resolve-global and yargs |
| Keywords | conventional-changelog, commitlint and cli |
rollup
Author: Rich Harris
Description: Next-generation ES module bundler
Homepage: https://rollupjs.org/
| Created | over 5 years ago |
| Last Updated | 4 days ago |
| License | MIT |
| Maintainers | 5 |
| Releases | 485 |
| Direct Dependencies | fsevents |
| Keywords | modules, bundler, bundling, es6 and optimizer |
README
# Rollup
package.jsonscriptsbuild/liveview.jsto usingrollupto bundle code (which was modified to use es6import/export)build/folder, it should get built!eslint-config-axwayfor linting code.npmignoreso we don't include build/CI/test files