kt3k / spn

:space_invader: Sprite Engine :space_invader:

spn v5.6.2

👾 SPrite eNgine 👾

What's this?

spn is a library for handling absolutely positioned elements effectively.

The responsibities of spn

• Dom layout in position: aboslute context
• Handle multiple display sizes
• Change image according to the current state of component

What spn doesn't do

• Dom layout in position: relative context
• Handle canvas
• Handle game progress (Not a game engine)

Supposed usecases

• Puzzle Game
• Action Game
• Role Playing Game
• Game in general

Dependencies

• jQuery
• capsid
• Promise

Usage

Via npm

npm install spn

const { Body } = require('spn')
const { component } = require('capsid')

@component
class MyCharacter extends Body {
    ...
}

API

const spn = require('spn')

spn.wait(time)

• @param {number} time The time to wait (in milliseconds)
• @return {Promise}

Returns the promise which resolves after the given milliseconds.

spn.reflow(elem)

• @param {jQuer} elem The element

Reflows (repaints) the element.

spn.Area

spn.Rect

spn.Body

spn.Animation

spn.Image

Traits

spn.being

spn.body

Decorator APIs

spn.ratio({x, y})

spn.margin({x, y, left, right, top, bottom})

spn.animation({show: [name, duration], hide: [name, duration]})

spn.width(width)

spn.height(height)

spn.transition.duration(duration)

History

• v3.10.0 2016-09-16 Added @margin() and @ratio() decorators.

License

MIT

spn's Issues

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

The devDependency rollup was updated from 1.6.0 to 1.6.1.

🚨 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

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for v1.6.1

2019-03-20

Bug Fixes

• Avoid name clashes of unused default exports when tree-shaking is false (#2758)
• Do not crash when generating SystemJS bundles containing array patterns with member expressions (#2760)

Pull Requests

• #2758: Make sure unused default exports are deconflicted when tree-shaking is false (@lukastaegert)
• #2760: Handle member expressions in array patterns (@lukastaegert)

Commits

The new version differs by 4 commits.

• dfe1713 1.6.1
• 7513859 Update changelog
• 8166eb0 Handle member expressions in array patterns (#2760)
• 26d2b31 Make sure unused default exports are deconflicted when tree-shaking is false (#2758)

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

The devDependency karma was updated from 3.1.1 to 3.1.2.

🚨 View failing branch.

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

karma 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

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for v3.1.2

Bug Fixes

• browser: report errors to console during singleRun=false (#3209) (30ff73b), closes #3131
• changelog: remove release which does not exist (#3214) (4e87902)
• dep: Bump useragent to fix HeadlessChrome version (#3201) (240209f), closes #2762
• deps: upgrade sinon-chai 2.x -> 3.x (#3207) (dc5f5de)
• file-list: do not preprocess up-to-date files (#3196) (5334d1a), closes #2829
• package: bump lodash version (#3203) (d38f344), closes #3177
• server: use flatted for json.stringify (#3220) (fb05fb1), closes #3215

Features

• docs: callout the key debug strategies. (#3219) (2682bff)

Commits

The new version differs by 11 commits.

• 7d4d347 chore: release v3.1.2
• 5077c18 chore: update contributors
• fb05fb1 fix(server): use flatted for json.stringify (#3220)
• 2682bff feat(docs): callout the key debug strategies. (#3219)
• 4e87902 fix(changelog): remove release which does not exist (#3214)
• 30ff73b fix(browser): report errors to console during singleRun=false (#3209)
• 5334d1a fix(file-list): do not preprocess up-to-date files (#3196)
• dc5f5de fix(deps): upgrade sinon-chai 2.x -> 3.x (#3207)
• d38f344 fix(package): bump lodash version (#3203)
• ffb41f9 refactor(browser): log state transitions in debug (#3202)
• 240209f fix(dep): Bump useragent to fix HeadlessChrome version (#3201)

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

The devDependency uglify-js was updated from 3.4.9 to 3.4.10.

🚨 View failing branch.

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

uglify-js 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

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for v3.4.10

 

Commits

The new version differs by 18 commits.

• 9707ccd v3.4.10
• cb8f3a2 add Node.js 10 to CI tests (#3342)
• 8b3259e fix corner case in reduce_vars (#3341)
• b66f47b update dependencies
• 8d2e6f3 fix function inlining after reduce_vars (#3340)
• b3ef5e5 enhance evaluate (#3339)
• 627f5fb fix corner case with nameCache (#3338)
• d90777b parse mangle.properties.regex in --config-file properly (#3337)
• e49297e improve usability of pure_funcs (#3336)
• ebd82b3 fix corner case in collapse_vars (#3334)
• d074aa6 fix corner case in collapse_vars (#3333)
• b052f62 fix corner case in reduce_vars (#3332)
• d4ac84b fix corner case in arguments & reduce_vars (#3331)
• e250396 fix corner case in arguments (#3330)
• c6fa39b Update README.md (#3311)

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

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

The devDependency prettier was updated from 1.16.4 to 1.17.0.

🚨 View failing branch.

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

prettier 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

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for Prettier 1.17: More quotes options and support for shared configs

🔗 Release Notes

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

The devDependency mocha was updated from 6.0.2 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.

mocha 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

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for v6.1.0

6.1.0 / 2019-04-07

🔒 Security Fixes

• #3845: Update dependency "js-yaml" to v3.13.0 per npm security advisory (@plroebuck)

🎉 Enhancements

• #3766: Make reporter constructor support optional options parameter (@plroebuck)
• #3760: Add support for config files with .jsonc extension (@sstephant)

📠 Deprecations

These are soft-deprecated, and will emit a warning upon use. Support will be removed in (likely) the next major version of Mocha:

• #3719: Deprecate this.skip() for "after all" hooks (@juergba)

🐛 Fixes

• #3829: Use cwd-relative pathname to load config file (@plroebuck)
• #3745: Fix async calls of this.skip() in "before each" hooks (@juergba)
• #3669: Enable --allow-uncaught for uncaught exceptions thrown inside hooks (@givanse)

and some regressions:

• #3848: Fix Suite cloning by copying root property (@fatso83)
• #3816: Guard against undefined timeout option (@boneskull)
• #3814: Update "yargs" in order to avoid deprecation message (@boneskull)
• #3788: Fix support for multiple node flags (@aginzberg)

📖 Documentation

• mochajs/mocha-examples: New repository of working examples of common configurations using mocha (@craigtaub)
• #3850: Remove pound icon showing on header hover on docs (@jd2rogers2)
• #3812: Add autoprefixer to documentation page CSS (@Munter)
• #3811: Update doc examples "tests.html" (@DavidLi119)
• #3807: Mocha website HTML tweaks (@plroebuck)
• #3793: Update config file example ".mocharc.yml" (@cspotcode)

🔩 Other

• #3830: Replace dependency "findup-sync" with "find-up" for faster startup (@cspotcode)
• #3799: Update devDependencies to fix many npm vulnerabilities (@XhmikosR)

Commits

The new version differs by 28 commits.

• f4fc95a Release v6.1.0
• bd29dbd update CHANGELOG for v6.1.0 [ci skip]
• aaf2b72 Use cwd-relative pathname to load config file (#3829)
• b079d24 upgrade deps as per npm audit fix; closes #3854
• e87c689 Deprecate this.skip() for "after all" hooks (#3719)
• 81cfa90 Copy Suite property "root" when cloning; closes #3847 (#3848)
• 8aa2fc4 Fix issue 3714, hide pound icon showing on hover header on docs page (#3850)
• 586bf78 Update JS-YAML to address security issue (#3845)
• d1024a3 Update doc examples "tests.html" (#3811)
• 1d570e0 Delete "/docs/example/chai.js"
• ade8b90 runner.js: "self.test" undefined in Browser (#3835)
• 0098147 Replace findup-sync with find-up for faster startup (#3830)
• d5ba121 Remove "package" flag from sample config file because it can only be passes as CLI arg (#3793)
• a3089ad update package-lock
• 75430ec Upgrade yargs-parser dependency to avoid loading 2 copies of yargs

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

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

The devDependency rollup was updated from 1.0.0 to 1.0.1.

🚨 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

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for v1.0.1

2019-01-03

Bug Fixes

• Properly handle reexporting an external default export for non-ESM targets when using named exports mode (#2620)
• Do not (wrongly) re-declare input options in the merged RollupOptions type (#2622)

Pull Requests

• #2620: Fixed issue with reexporting default as default with {exports: named, interop: true} options (@Andarist)
• #2622: Simplify RollupOptions (@Kinrany)
• #2627: Show how to skip imports for optional plugins (@chris-morgan)

Commits

The new version differs by 6 commits.

• fbb5f9e 1.0.1
• e7b3c78 Update changelog
• eda15fa Update changelog
• 5ff6352 Show how to skip imports for optional plugins (#2627)
• 6d32530 Simplify RollupOptions (#2622)
• f5364d9 Fixed issue with reexporting default as default with {exports: named, interop: true} options. (#2620)

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

There have been updates to the babel7 monorepo:

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

• The devDependency @babel/preset-env was updated from 7.3.4 to 7.4.0.

🚨 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

• ❌ ci/circleci: Your tests failed on CircleCI (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 jquery is breaking the build 🚨

Version 3.2.0 of jquery just got published.

Branch	Build failing 🚨
Dependency	jquery
Current Version	3.1.1
Type	devDependency

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

As jquery 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

• ❌ ci/circleci Your tests failed on CircleCI 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 jquery is breaking the build 🚨

The devDependency jquery was updated from 3.3.1 to 3.4.0.

🚨 View failing branch.

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

jquery 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

• ❌ ci/circleci: Your tests failed on CircleCI (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 watchify is breaking the build 🚨

The devDependency watchify was updated from 3.11.0 to 3.11.1.

🚨 View failing branch.

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

watchify 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

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Commits

The new version differs by 8 commits.

• c3fe218 3.11.1
• e90101b Merge pull request #362 from digipost/upgrade-deps
• d163b4f upgrade dependencies: fix errors from npm audit
• 1917270 Merge pull request #351 from menzow/feature/update-docs
• d232754 Merge pull request #357 from Kamil93/patch-1
• d924e9b Update readme.markdown
• 9ea8a65 Support for working with transforms
• 8147bc5 Add troubleshooting information for silenced errors

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

The devDependency prettier 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.

prettier 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

• ❌ ci/circleci: Your tests failed on CircleCI (Details).

---

Release Notes for 1.14.3

🔗 Changelog

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 🌴