Giter VIP home page Giter VIP logo

ember-cli-pixijs's People

Contributors

cibernox avatar ember-tomster avatar ferdev avatar geekygrappler avatar greenkeeper[bot] avatar jayjayjpg avatar mansona avatar marcoow avatar pangratz avatar schnellesadlerauge avatar turbo87 avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar

ember-cli-pixijs's Issues

An in-range update of ember-cli-dependency-checker is breaking the build 🚨

Version 2.0.1 of ember-cli-dependency-checker just got published.

Branch Build failing 🚨
Dependency ember-cli-dependency-checker
Current Version 2.0.0
Type devDependency

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

As ember-cli-dependency-checker 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 failed Details

Commits

The new version differs by 3 commits.

  • fa28114 v2.0.1
  • 8c5a979 Merge pull request #77 from kanongil/resolved-check
  • bca8aa5 Also check shrinkwrap version against "_resolved" field. Fixes #76

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 loader.js is breaking the build 🚨

Version 4.2.0 of loader.js just got published.

Branch Build failing 🚨
Dependency loader.js
Current Version 4.1.0
Type devDependency

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

As loader.js 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 14 commits .

  • cc53069 release v4.2.0
  • 1a453d3 Merge pull request #104 from trentmwillis/redefine
  • 93478ef Improve redefinition scenarios
  • e289916 Fix test:dev command
  • 287a487 Merge pull request #105 from trentmwillis/clarify
  • cda1c29 Clarify prime comment
  • 562ecf1 Merge pull request #100 from jrowlingson/master
  • 6a9b916 remove petal references
  • b609262 Merge pull request #95 from chadhietala/heimdall-instrumentation
  • c49296d Instrument with heimdall
  • 453fe8c Merge pull request #97 from Turbo87/ci-deploy
  • 37fef79 CI: Enable automatic NPM deployment for tags
  • c4f0755 Merge pull request #96 from chadhietala/dict-registry
  • 8a34296 Use dict for registery and seen to avoid filling IC cache

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 ember-cli-inject-live-reload is breaking the build 🚨

Version 1.7.0 of ember-cli-inject-live-reload just got published.

Branch Build failing 🚨
Dependency ember-cli-inject-live-reload
Current Version 1.6.1
Type devDependency

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

As ember-cli-inject-live-reload 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 failed Details

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

Version 4.2.0 of ember-resolver just got published.

Branch Build failing 🚨
Dependency ember-resolver
Current Version 4.1.0
Type devDependency

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

As ember-resolver 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 failed Details

Commits

The new version differs by 13 commits.

  • 218f83c v4.2.0
  • dd8a476 Merge pull request #199 from ember-cli/ember-cli
  • d041f7c Bump ember-cli (w/o eslint)
  • 6614e68 Merge pull request #198 from ember-cli/pass-referrer-v2
  • 5f425d6 Normalize referrer and lookupString, add config flag
  • d153cc8 Merge pull request #192 from 201-created/defaultType
  • aec0059 defaultType support, mv partials code to resolver
  • 9dec996 Merge pull request #190 from 201-created/no-normalize
  • 8d97d8b Assert against get, not normalize
  • d87ce8e Merge pull request #186 from ember-cli/typo
  • d0ad411 fix file name typo
  • 8ae3114 Merge pull request #184 from acorncom/patch-1
  • 5c20636 Fixes a small typo

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 broccoli-merge-trees is breaking the build 🚨

Version 1.2.2 of broccoli-merge-trees just got published.

Branch Build failing 🚨
Dependency broccoli-merge-trees
Current Version 1.2.1
Type dependency

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

As broccoli-merge-trees is a direct dependency of this project this is very likely breaking your project right now. If other packages depend on you it’s very likely also breaking them.
I recommend you give this issue a very high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details
Commits

The new version differs by 3 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 ember-cli-htmlbars is breaking the build 🚨

Version 1.3.1 of ember-cli-htmlbars just got published.

Branch Build failing 🚨
Dependency ember-cli-htmlbars
Current Version 1.3.0
Type devDependency

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

As ember-cli-htmlbars 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 failed Details

Commits

The new version differs by 4 commits0.

  • b46eb48 v1.3.1
  • f0c03ec Merge pull request #109 from ember-cli/use-non-deprecated-version-checker-api
  • faf7f25 Add yarn.lock.
  • 1b27f67 Update ember-cli-version-checker use to avoid deprecated APIs.

false

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 🌴

Missing module error on Ember, EmberCLI 3.5.0

I created a component using the code from this repo's README and I am getting this error in the console:

Uncaught Error: Could not find module `ember` imported from `ember-cli-pixijs/components/pixi-canvas`

Here is my component code:

import PIXI from "pixi";
import PixiCanvas from "ember-cli-pixijs/components/pixi-canvas";

export default PixiCanvas.extend({
  draw() {
    const renderer = this.get('pixiRenderer');
    const stage = new PIXI.Container();
    const graphics = new PIXI.Graphics();

    graphics.beginFill(0xFF3300);
    graphics.lineStyle(10, 0xffd900, 1);

    graphics.moveTo(50, 50);
    graphics.lineTo(250, 50);
    graphics.lineTo(100, 100);
    graphics.lineTo(250, 220);
    graphics.lineTo(50, 220);
    graphics.lineTo(50, 50);
    graphics.endFill();

    stage.addChild(graphics);
    renderer.render(stage);
  }
});

Contents of package.json:

{
  "name": "pixi-app",
  "version": "0.0.0",
  "private": true,
  "description": "Small description goes here",
  "repository": "",
  "license": "MIT",
  "author": "",
  "directories": {
    "doc": "doc",
    "test": "tests"
  },
  "scripts": {
    "build": "ember build",
    "lint:hbs": "ember-template-lint .",
    "lint:js": "eslint .",
    "start": "ember serve",
    "test": "ember test"
  },
  "devDependencies": {
    "@ember/jquery": "^0.5.2",
    "@ember/optional-features": "^0.6.3",
    "active-model-adapter": "^2.2.0",
    "bootstrap": "^4.1.3",
    "broccoli-asset-rev": "^2.7.0",
    "ember-ajax": "^3.1.0",
    "ember-auto-import": "^1.2.13",
    "ember-bootstrap": "^2.1.2",
    "ember-cli": "~3.5.0",
    "ember-cli-app-version": "^3.2.0",
    "ember-cli-babel": "^6.16.0",
    "ember-cli-dependency-checker": "^3.0.0",
    "ember-cli-dotenv": "^2.2.1",
    "ember-cli-eslint": "^4.2.3",
    "ember-cli-flash": "^1.6.6",
    "ember-cli-htmlbars": "^3.0.0",
    "ember-cli-htmlbars-inline-precompile": "^1.0.3",
    "ember-cli-inject-live-reload": "^1.8.2",
    "ember-cli-mirage": "^0.4.9",
    "ember-cli-moment-shim": "^3.7.1",
    "ember-cli-pixijs": "0.0.2",
    "ember-cli-sass": "^8.0.1",
    "ember-cli-sri": "^2.1.1",
    "ember-cli-template-lint": "^1.0.0-beta.1",
    "ember-cli-uglify": "^2.1.0",
    "ember-data": "~3.4.0",
    "ember-data-has-many-query": "^0.2.0",
    "ember-export-application-global": "^2.0.0",
    "ember-get-config": "^0.2.4",
    "ember-kohactivated": "0.0.2",
    "ember-load-initializers": "^1.1.0",
    "ember-lodash": "^4.18.0",
    "ember-maybe-import-regenerator": "^0.1.6",
    "ember-moment": "^7.8.0",
    "ember-qunit": "^3.4.1",
    "ember-resolver": "^5.0.1",
    "ember-simple-auth": "^1.7.0",
    "ember-source": "~3.5.0",
    "ember-truth-helpers": "^2.1.0",
    "eslint-plugin-ember": "^5.2.0",
    "loader.js": "^4.7.0",
    "qunit-dom": "^0.8.0",
    "sass": "^1.14.2"
  },
  "engines": {
    "node": "6.* || 8.* || >= 10.*"
  }
}

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
  • The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

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 eslint-plugin-mocha is breaking the build 🚨

Version 4.11.0 of eslint-plugin-mocha just got published.

Branch Build failing 🚨
Dependency eslint-plugin-mocha
Current Version 4.10.1
Type devDependency

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

As eslint-plugin-mocha 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 failed Details

Release Notes 4.11.0

Enhancements

  • Added support for async functions in no-synchronous-tests (#138)
Commits

The new version differs by 4 commits.

  • 91d608b 4.11.0
  • d40bbfe Merge pull request #138 from jawadst/async-functions
  • 64835a4 no-synchronous-tests: using ast utils + JSON schema for options
  • 9fc05c4 Added support for async functions in no-synchronous-tests

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

Version 2.14.0 of ember-data just got published.

Branch Build failing 🚨
Dependency ember-data
Current Version 2.13.2
Type devDependency

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

As ember-data 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 failed Details

Commits

The new version differs by 140 commits ahead by 140, behind by 34.

  • 1eef0e9 Release Ember Data 2.14.0
  • fba75be Update changelog for the Ember Data 2.14.0 release
  • 584d159 [BUGFIX] fixes an issue with sync dematerialization followed by a findRecord, adds test coverage (#5013)
  • d4b9430 such travis (#5015)
  • 2a787d7 Release Ember Data 2.14.0-beta.3s
  • d4fa2d5 Update changelog for Ember Data 2.14.0-beta.2 release
  • cbe22b7 [BUGFIX BETA] Added system/store/container-instance-cache to the -private export file
  • 751e815 Release Ember Data 2.14.0-beta.2
  • 58d1c23 Fix typo in function call
  • 7f65001 [BUGFIX beta] Ensure Engines can boot without error.
  • 3c9e2c4 [BUGFIX] remove forgotten broccoli-stew import
  • d4dc00c [BUGFIX beta] Skip test which doesn't play nicely with the latest ember-cli and is failing on master
  • c42ded8 Release 2.14.0-beta.1
  • 4304c47 Merge pull request #4950 from runspired/fix/error-on-let-closures
  • 097ad90 start guarding against poorly optimized babel output

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

An in-range update of eslint-plugin-ember is breaking the build 🚨

Version 3.5.0 of eslint-plugin-ember just got published.

Branch Build failing 🚨
Dependency eslint-plugin-ember
Current Version 3.4.1
Type devDependency

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

As eslint-plugin-ember 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 failed Details

Release Notes v3.5.0
  • ⚙️ #77 - Add no-capital-letters-in-routes to base config
  • ⭐️ #80 - alias-model-in-controller: allow nested properties
Commits

The new version differs by 3 commits.

  • 0b66ed1 3.5.0
  • 691aa24 alias-model-in-controller: allow nested properties (#80)
  • 390dc0f add the rule into base with default of 2 (error) (#77)

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 loader.js is breaking the build 🚨

Version 4.5.0 of loader.js just got published.

Branch Build failing 🚨
Dependency loader.js
Current Version 4.4.1
Type devDependency

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

As loader.js 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 7 commits.

  • 094e20b release v4.5.0 🎉
  • db2f6a6 Merge pull request #126 from ember-cli/moduleId
  • 204838b rename mod.name => mod.id
  • 4fa0fe0 add require.moduleId to allow a module to know its ID
  • f62bc54 Merge pull request #121 from ember-cli/define-exports
  • d963886 Update README.md
  • 928e18f add define.exports

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.