Git Product home page Git Product logo

fixture's Introduction

@unional/fixture

NPM version NPM downloads

GitHub NodeJS Codecov

Semantic Release

Visual Studio Code

Provides fixture for tests. You can use it for any test runner such as jest, ava, mocha, tap, etc.

Install

# npm
npm install -D @unional/fixture

# yarn
yarn add -D @unional/fixture

# pnpm
pnpm install -D @unional/fixture

# rush
rush add -p @unional/fixture --dev

Usage

baseline() is the heart of @unional/fixture. You can use it to read a folder containing multiple test cases and use them in your test runner.

import { baseline } from '@unional/fixture'

// basic usage
baseline('fixtures', ({ caseName, caseType, casePath, resultPath, match, copyToBaseline }) => {
  // `test()` comes from your favorite test runner.
  // e.g. `ava`, `jest`, `mocha`
  test(caseName, async () => {
    // this example assumes `caseType === 'file'`,
    // so the `casePath` points to the input file directly.
    fs.readFileSync(casePath, 'utf-8')

    // `resultPath` points to a folder where you can save your result(s)
    fs.writeFileSync(path.join(resultPath, 'output.txt', '<some data>'))

    // compare result and baseline folder
    await match()

    // match compares specific file in result folder and baseline folder
    await match('output.txt')

    // if you are happy with the change,
    // use this to copy the artifacts from result folder to baseline folder,
    // or you can do that manually from your IDE.
    await copyToBaseline('*.txt')
  })

  // advance usage
  baseline({
    basePath: 'fixtures',
    // default: 'cases'
    casesFolder: 'scenarios',
    // default: 'results'
    resultsFolder: 'actuals',
    // default: 'baselines'
    baselinesFolder: 'expects',
    // filter for specific cases
    // can use wildcards or RegExp
    filter: '*.pass',
    // By default warning messages will be displayed when some test cases are filtered.
    // Use this to suppress those warnings.
    suppressFilterWarnings: true,
    // If the file has more lines than this threshold,
    // then the file will be diff with line numbers,
    // and the unchanged lines will be trimmed off.
    largeFileThreshold: 100,
    // Controls how many unchanged lines will be shown around the changes.
    largeFileAmbientLines: 5,
    /**
     * Maximum number of diff lines to show.
     * If there are more diff lines,
     * the remaining will be timmed and show a summary instead.
     */
    diffDisplayThreshold: 150
  }, (context) => {
    ...
  })
})

Command Testing

In addition to baseline(), @unional/fixture provides execCommand() and writeCommandResult() to run command line test within the fixture.

If the test case is a JSON or YAML, it will read and execute the command within. If the test case is a folder, it will look for a command.json|yml|yaml in the folder and does the same.

More file types and features will be added in the future.

Here is a common way to use them:

import { baseline, execCommand, writeCommandResult } from '@unional/fixture'

baseline('fixtures/command', ({ caseType, caseName, casePath, resultPath, match }) => {
  it(caseName, async () => {
    writeCommandResult(
      resultPath,
      await execCommand({ caseType, caseName, casePath })
    )
    return match()
  })
})

The execCommand() has an alternative signature that allows you to easily run and capture stdout and stderr:

const { stdout, stderr } = await execCommand({ casePath, command, args })

Contribute

# right after fork
yarn

# begin making changes
git checkout -b <branch>
yarn 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

Commands

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

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

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

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

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

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

fixture's People

Contributors

artemgovorov avatar dependabot[bot] avatar greenkeeper[bot] avatar omgimalexis avatar renovate-bot avatar renovate[bot] avatar semantic-release-bot avatar unional avatar

Stargazers

 avatar  avatar

Watchers

 avatar  avatar  avatar

fixture's Issues

An in-range update of @unional/devpkg-node is breaking the build 🚨

The devDependency @unional/devpkg-node was updated from 1.1.2 to 1.1.3.

🚨 View failing branch.

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

@unional/devpkg-node 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).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked

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

The devDependency semantic-release was updated from 15.12.4 to 15.12.5.

🚨 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 failed (Details).
  • βœ… all: * node-latest - Success

Release Notes for v15.12.5

15.12.5 (2018-12-11)

Bug Fixes

  • allow to set ci option via API and config file (862ec4c)
Commits

The new version differs by 8 commits.

  • 649b530 docs: mention that debug option is CLI only
  • 862ec4c fix: allow to set ci option via API and config file
  • 6b110b6 docs: switch to spectrum.chat
  • e4c6649 docs: syntax fixes in plugins list
  • 6220641 docs: add @semantic-release/apm to plugins list
  • a45273e docs: add maven-semantic-release to list of community plugins
  • d109113 chore(package): update nyc and sinon
  • cd69583 test: delete unused test helper file

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

The dependency chalk was updated from 2.4.1 to 2.4.2.

🚨 View failing branch.

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

chalk is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked

Release Notes for v2.4.2

This release is done from the v2-release branch, as master branch targets the work-in-progress v3 release.

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 🌴

An in-range update of cp-file is breaking the build 🚨

The dependency cp-file was updated from 6.0.0 to 6.1.0.

🚨 View failing branch.

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

cp-file is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked

Release Notes for v6.1.0

v6.0.0...v6.1.0

Commits

The new version differs by 4 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 🌴

add sandbox support

Copy the case to a sandbox, allow customizing the sandbox and execute there, then returning the result to be used in resultPath

An in-range update of @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.12.12 to 10.12.13.

🚨 View failing branch.

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

@types/node 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).
  • βœ… all: * node-latest - Success

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 @unional/logging is breaking the build 🚨

The dependency @unional/logging was updated from 0.5.3 to 0.5.4.

🚨 View failing branch.

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

@unional/logging is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked

Release Notes for v0.5.4

0.5.4 (2018-12-28)

Bug Fixes

Commits

The new version differs by 2 commits.

  • 2477831 fix: log level can use any number (#35)
  • 735d4ea chore: update project to latest standard (#34)

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 🌴

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


Invalid npm token.

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 πŸ“¦πŸš€

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

The devDependency assertron was updated from 5.2.2 to 5.2.3.

🚨 View failing branch.

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

assertron 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).
  • βœ… all: * node-latest - Success

Release Notes for v5.2.3

5.2.3 (2018-12-10)

Bug Fixes

  • skip perf_hooks using package.json/browser field (#111) (d7a3367)
Commits

The new version differs by 3 commits.

  • 3414e7e build: disable greenkeeeper, semver, and codecov on travis
  • ca69771 doc: update badges
  • d7a3367 fix: skip perf_hooks using package.json/browser field (#111)

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

The devDependency assertron was updated from 5.1.4 to 5.2.0.

🚨 View failing branch.

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

assertron 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 v5.2.0

5.2.0 (2018-10-21)

Features

Commits

The new version differs by 2 commits.

  • 7d2fb01 feat: add equal and deepEqual (#109)
  • 32a9589 Update tslint-config-unional to the latest version πŸš€ (#108)

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

The devDependency path-equal was updated from 1.1.0 to 1.1.1.

🚨 View failing branch.

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

path-equal 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).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked

Release Notes for v1.1.1

1.1.1 (2019-01-28)

Bug Fixes

Commits

The new version differs by 8 commits.

  • 6a45aa4 fix: parent '..' (#18)
  • 0d99aa3 chore: misc clean up
  • c0580a1 chore: remove extra dep on semantic-release
  • 1679bb7 chore: update project
  • 11bcc01 Update README.md
  • 51350f8 misc: update deps (#12)
  • 2199c7c Update eslint to the latest version πŸš€ (#8)
  • b7e096e refactor: misc clean up

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 @types/node is breaking the build 🚨

The devDependency @types/node was updated from 10.11.7 to 10.12.0.

🚨 View failing branch.

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

@types/node 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).

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 @types/diff is breaking the build 🚨

The devDependency @types/diff was updated from 3.5.2 to 3.5.3.

🚨 View failing branch.

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

@types/diff 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).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked

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 🌴

Decouple case and result structure

Case using folder doesn't mean result will also be a folder.

match() should check whether the target is a file or folder and perform the right logic.

On the other hand, asking user to create the result folder when needed is a hassle.

We can provide a helper function for it, and use mkdirp internally.

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

The dependency glob was updated from 7.1.3 to 7.1.4.

🚨 View failing branch.

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

glob is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • node8 - Blocked

Commits

The new version differs by 5 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 jest-audio-reporter is breaking the build 🚨

The devDependency jest-audio-reporter was updated from 2.2.0 to 2.2.1.

🚨 View failing branch.

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

jest-audio-reporter 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).
  • βœ… all: * node-latest - Success

Release Notes for v2.2.1

2.2.1 (2018-12-19)

Bug Fixes

Commits

The new version differs by 1 commits.

  • 68e98fa fix: update play-sound (#28)

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 🌴

Dependency Dashboard

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

  • chore(deps): update dependency esbuild to ^0.21.0
  • chore(deps): update dependency eslint to v8.57.0
  • chore(deps): update dependency @repobuddy/jest to v4
  • chore(deps): update dependency @types/mkdirp to v2
  • chore(deps): update dependency @types/node to v20
  • chore(deps): update dependency @types/rimraf to v4
  • chore(deps): update dependency eslint to v9
  • chore(deps): update dependency husky to v9
  • chore(deps): update github/codeql-action action to v3
  • fix(deps): update dependency cp-file to v11
  • fix(deps): update dependency dir-compare to v5
  • fix(deps): update dependency execa to v9
  • πŸ” Create all rate-limited PRs at once πŸ”

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

Detected dependencies

github-actions
.github/workflows/codeql-analysis.yml
  • actions/checkout v4@b4ffde65f46336ab88eb53be808477a3936bae11
  • github/codeql-action v2
  • github/codeql-action v2
  • github/codeql-action v2
.github/workflows/pull-request.yml
.github/workflows/release.yml
npm
package.json
  • @types/diff-match-patch ^1.0.32
  • chalk ^5.2.0
  • cp-file ^10.0.0
  • diff-match-patch ^1.0.5
  • diff-match-patch-line-and-word ^0.1.3
  • dir-compare ^4.0.0
  • execa ^7.0.0
  • glob ^8.0.3
  • iso-error ^6.0.0
  • js-yaml ^4.1.0
  • minimatch ^8.0.0
  • mkdirp ^2.0.0
  • pad-left ^2.1.0
  • rimraf ^3.0.2
  • standard-log ^11.5.0
  • standard-log-color ^12.0.0
  • tersify ^3.11.1
  • type-plus ^7.0.0
  • @commitlint/cli ^17.3.0
  • @commitlint/config-conventional ^17.3.0
  • @repobuddy/jest ^2.2.1
  • @semantic-release/changelog ^6.0.2
  • @semantic-release/git ^10.0.1
  • @semantic-release/github ^8.0.7
  • @semantic-release/npm ^9.0.1
  • @types/glob ^8.0.0
  • @types/jest ^29.2.4
  • @types/js-yaml ^4.0.5
  • @types/mkdirp ^1.0.2
  • @types/node ^18.0.0
  • @types/rimraf ^3.0.2
  • @typescript-eslint/eslint-plugin ^5.46.0
  • assertron ^11.0.2
  • cross-env ^7.0.3
  • depcheck ^1.4.3
  • esbuild ^0.19.0
  • eslint 8.51.0
  • eslint-plugin-harmony ^7.1.1
  • husky ^8.0.2
  • jest ^29.3.1
  • jest-watch-suspend ^1.1.2
  • jest-watch-toggle-config-2 ^2.1.0
  • jest-watch-typeahead ^2.2.1
  • ncp ^2.0.0
  • npm-run-all ^4.1.5
  • path-equal ^1.2.5
  • pinst ^3.0.0
  • semantic-release ^19.0.5
  • ts-jest ^29.0.3
  • typescript ^5.0.0
  • uncolor ^0.4.0

  • Check this box to trigger a request for Renovate to run again on this repository

The automated release is failing 🚨

🚨 The automated release from the main branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug fixes and new features again.

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 fix 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 main branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here are 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.


Invalid npm token.

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 for your account, set its level to "Authorization only" in your account settings. semantic-release cannot publish with the default "
Authorization 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 πŸ“¦πŸš€

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

The dependency unpartial was updated from 0.6.2 to 0.6.3.

🚨 View failing branch.

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

unpartial is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked
  • node9 - Blocked
  • node10 - Blocked

Release Notes for v0.6.3

0.6.3 (2019-05-13)

Bug Fixes

Commits

The new version differs by 1 commits.

  • 0571b9a fix: array with undefined (#29)

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

The dependency dir-compare was updated from 1.4.0 to 1.5.0.

🚨 View failing branch.

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

dir-compare is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked

Commits

The new version differs by 5 commits.

  • ee4fabc v1.5.0
  • e5a3d54 Update ci config
  • 408fd26 Add option to ignore line endings and white space differences #10
  • 2beee77 add ci tests #8
  • 635d0e0 Fix loop detection to properly account for parent symlinks

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 @unional/devpkg-node is breaking the build 🚨

The devDependency @unional/devpkg-node was updated from 1.1.4 to 1.1.5.

🚨 View failing branch.

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

@unional/devpkg-node 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).
  • ❌ all: * node-latest - Failed
  • node8 - Blocked

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 🌴

An in-range update of @unional/devpkg-node is breaking the build 🚨

The devDependency @unional/devpkg-node was updated from 1.3.2 to 1.3.3.

🚨 View failing branch.

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

@unional/devpkg-node 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).
  • ❌ all: * node-latest - Failed
  • node9 - Blocked
  • node10 - Blocked
  • node8 - Blocked

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 🌴

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.