ajihyf/pixi-dom

pixi-dom's Issues

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

The devDependency @types/webpack-env was updated from 1.13.8 to 1.13.9.

🚨 View failing branch.

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

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

---

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

The devDependency rollup was updated from 1.4.1 to 1.4.2.

🚨 View failing branch.

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

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

---

Release Notes for v1.4.2

2019-03-07

Bug Fixes

• Respect variable identity of exports when hashing (#2741)
• Resolve a situations where a variable was imported twice with the same name (#2737)

Pull Requests

• #2741: Fix hashing when different variable are exported using the same name (@lukastaegert)
• #2737: Fix duplicate imports with conflicting names (@lukastaegert)

Commits

The new version differs by 6 commits.

• adaa23e 1.4.2
• 2d03a67 Update changelog
• 858fea4 Resolve a situation where different default exports referencing the same (#2737)
• 6903425 Update changelog
• af41561 Fix an issue where the same hash was generated when different variables (#2741)
• d27c0f6 Docs: Fix return type (#2738)

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 rollup-plugin-typescript2 is breaking the build 🚨

The devDependency rollup-plugin-typescript2 was updated from 0.19.2 to 0.19.3.

🚨 View failing branch.

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

rollup-plugin-typescript2 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 0.19.3

Fix for cache

Commits

The new version differs by 3 commits.

• e9070ab - building with rollup 1.2.3
• ac9b15d - fix for #137
• 4bf049f - package version

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 11.10.4 to 11.10.5.

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

---

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 start-server-and-test is breaking the build 🚨

The devDependency start-server-and-test was updated from 1.7.11 to 1.7.12.

🚨 View failing branch.

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

start-server-and-test 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).

---

Release Notes for v1.7.12

1.7.12 (2019-03-15)

Bug Fixes

• deps: update dependency debug to v4 (#100) (bd075d8)

Commits

The new version differs by 14 commits.

• bd075d8 fix(deps): update dependency debug to v4 (#100)
• 4efa0c8 chore(deps): update dependency mocha to v6 (#150)
• 5b2b9e4 chore(deps): update dependency semantic-release to v15.13.3
• e143380 chore(deps): update dependency semantic-release to v15.13.2
• 8ad4d9f chore(deps): update dependency dependency-check to v3.3.0
• 8340680 chore(deps): update dependency semantic-release to v15.13.1
• 9494f70 chore(deps): update dependency travis-deploy-once to v5.0.11
• 13a35e8 chore(deps): update dependency semantic-release to v15.13.0
• f4ea3d5 chore(deps): update dependency license-checker to v24.1.0
• 98e8bc1 chore(deps): update dependency travis-deploy-once to v5.0.10
• 470dcf6 chore(deps): update dependency semantic-release to v15.12.5
• c66e65e chore(deps): update dependency semantic-release to v15.12.4
• 6194e9f chore(deps): update dependency semantic-release to v15.12.3
• 2113027 chore(deps): update dependency semantic-release to v15.12.2

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

The devDependency rollup was updated from 1.14.2 to 1.14.3.

🚨 View failing branch.

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

rollup 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 v1.14.3

2019-06-06

Bug Fixes

• Generate correct external imports when importing from a directory that would be above the root of the current working directory (#2902)

Pull Requests

• #2902: Use browser relative path algorithm for chunks (@lukastaegert)

Commits

The new version differs by 4 commits.

• c68bd95 1.14.3
• d79aa57 Update changelog
• 7179390 Use browser relative path algorithm for chunks (#2902)
• b1df517 Add funding button

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

The devDependency @types/puppeteer was updated from 1.12.1 to 1.12.2.

🚨 View failing branch.

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

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

---

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

The devDependency @types/jest was updated from 24.0.9 to 24.0.10.

🚨 View failing branch.

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

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

---

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 🌴

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper 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 click the 'fix repo' button on account.greenkeeper.io.

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

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.3.3 to 7.3.4.

🚨 View failing branch.

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

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 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 🌴