Giter VIP home page Giter VIP logo

ember-sticky-element's Introduction

ember-sticky-element

Build Status Ember Observer Score npm version Greenkeeper badge

This Ember addon gives you the ability to make parts of your UI stick to the viewport when scrolling. Its semantics follow roughly the proposed position: sticky specs.

See the Demo App for some examples!

Why should I use this

The mentioned CSS extension of position: sticky is still in a draft stage, and not widely supported natively. While there are polyfills available, they lack some features:

  • you cannot change the styling of your sticky element based on its state of being sticky or not
  • you cannot dynamically change the contents of the sticky element based on that state either

While there a probably a few jQuery plugins around for the same purpose, they might not always play well with Ember.

So this addon adds a sticky-element component, that mimics the basic position: sticky behaviour. Currently it only supports scrolling in the vertical direction, not horizontal stickiness yet.

It leverages ember-in-viewport under the hood for its efficient viewport detection techniques.

Compatibility

  • Ember.js v2.18 or above
  • Ember CLI v2.13 or above
  • Node.js v8 or above

Installation

ember install ember-sticky-element

Usage

Just wrap your content into the sticky-element:

{{#sticky-element}}
  <h2>Sticky Element</h2>
{{/sticky-element}}

This will make it flow with the other content when scrolling until it reaches the top of the viewport, at which point it will get sticky. This effectively makes it position: fixed. (Unfortunately for now this will require you to allow inline styles if you use CSP!)

Customization options

Offsets

The behaviour of the component and its styling can be customized with the following options. Also see the Demo App for some examples.

Top offset

Add the top property to specify an offset in pixels from the top of the viewport:

{{#sticky-element top=50}}
  <h2>Sticky Element</h2>
{{/sticky-element}}
Bottom offset

By default the sticky element will not care about its parent enclosing element and just remain sticky to the top when scrolling the page all the way down. To make it also stick to the bottom of its parent (so it does not leave its parent's boundaries), just add the bottom property, with a value of 0 or some other offset:

{{#sticky-element top=50 bottom=0}}
  <h2>Sticky Element</h2>
{{/sticky-element}}

Make sure that the parent element has some positioning applied, so at least position: relative, as sticking to the bottom is done by applying position: absolute to the sticky element!

Disabling

You can set the enabled property to false to disable the sticky behavior:

{{#sticky-element enabled=someBooleanProperty}}
  <h2>Sticky Element</h2>
{{/sticky-element}}

Styling

CSS

The sticky element has a containerClassName property you can use for styling (by default .sticky-element). Furthermore additionals classes can be set: when being sticky:

  • containerStickyClassName (by default .sticky-element--sticky): when sticked either to the top or the bottom.
  • containerStickyTopClassName (by default .sticky-element--sticky-top): when sticked to the top.
  • containerStickyBottomClassName (by default .sticky-element--sticky-bottom): when sticked to the bottom.
Content

The component yields a hash, that contains the following boolean properties based on its state:

  • isSticky
  • isStickyTop
  • isStickyBottom

You can use these to change the content of the sticky element based on its state:

{{#sticky-element as |state|}}
  <h2>Sticky Element</h2>
  <p>{{#if state.isSticky}}Yeah, I am sticky!{{else}}I am just a normal element.{{/if}}</p>
{{/sticky-element}}

Contributing

See the Contributing guide for details.

License

This project is licensed under the MIT License.

ember-sticky-element's People

Contributors

anthony-mangano-argus avatar ctjhoa avatar dependabot[bot] avatar ember-tomster avatar greenkeeper[bot] avatar joshkg avatar ncoden avatar simonihmig avatar

Stargazers

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

Watchers

 avatar  avatar  avatar  avatar

ember-sticky-element's Issues

Wrapper element gets wrong height if content changes when sticky

The height assigned to sticky-element-container when the element becomes sticky appears to be calculated before isSticky in the yielded hash becomes true, which can result in either a gap between the sticky element and subsequent content (if the element gets smaller when sticky) or the sticky element covering up some of the subsequent content (if the element gets larger when sticky).

In order to test this / see it in action, you can add the following extra columns to the demo app:

  <div class="col off">
    {{#sticky-element class="sticky" as |sticky|}}
      {{#if sticky.isSticky}}
        <div style="height: 50px;background-color:#f00;"></div>
      {{else}}
        <div style="height: 250px;background-color:#f00;"></div>
      {{/if}}
      <p>small, not sticky to bottom, off view, shrinks when sticky</p>
      <p class="debug">
        {{sticky-debug sticky}}
      </p>
    {{/sticky-element}}
    <p>This bit isn't sticky.</p>
  </div>

  <div class="col off">
    {{#sticky-element class="sticky" as |sticky|}}
      {{#if sticky.isSticky}}
        <div style="height: 250px;background-color:#f00;"></div>
      {{else}}
        <div style="height: 50px;background-color:#f00;"></div>
      {{/if}}
      <p>small, not sticky to bottom, off view, grows when sticky</p>
      <p class="debug">
        {{sticky-debug sticky}}
      </p>
    {{/sticky-element}}
    <p>This bit isn't sticky.</p>
  </div>

When you scroll far enough for the elements to stick to the top, the first column will have a gap between the sticky element and the "This bit isn't sticky" text, whereas the "isn't sticky" text in the second column will disappear behind the sticky element.

Width on sticky component not updating on resize

I can see that the component is setting the width in an inline style -- however if I resize my browser (shrinking) the width is not updating along with it, breaking layout.

Can we add an option to set the width (in my case, 100% would do it) or at least throw a classNames property on the component so I can set it via CSS? Thanks! Great addon!

An in-range update of ember-cli-inject-live-reload is breaking the build 🚨

The devDependency ember-cli-inject-live-reload was updated from 1.8.2 to 1.10.0.

🚨 View failing branch.

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

ember-cli-inject-live-reload 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).

Commits

The new version differs by 9 commits.

  • 60b2ba2 1.10.0
  • 415935b Add yarn.lock.
  • 542a2a0 Migrate to lerna-changelog + add 1.10.0 to changelog.
  • a21fd1d Merge pull request #55 from SparshithNR/path-fix
  • f6d8238 Provide backward compatibility.
  • ab29353 Pass path as argument to livereload.js
  • 68c237e release v1.9.0 🎉
  • 2e88996 Merge pull request #54 from SparshithNR/test-refactor
  • fcd41eb Refactoring and Tests

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 🌴

feature request: footer sticky

My use-case is the inverse of a sticky header. I want to stick a footer to the bottom if the footer is somewhere below the fold and the view is in the parent element. I tried this, and nothing currently happens when just setting bottom.

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

The devDependency ember-cli-sri was updated from 2.1.0 to 2.1.1.

🚨 View failing branch.

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

ember-cli-sri 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).

Commits

The new version differs by 4 commits.

  • 25a6506 release v2.1.1
  • 11eb96d Merge pull request #27 from alobaidizt/whitelist-files
  • 1c7b65d Whitelist in package.json only required files
  • da9910f Merge pull request #22 from jonathanKingston/bump-version/2.1.0

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

The devDependency ember-cli-qunit was updated from 4.3.2 to 4.4.0.

🚨 View failing branch.

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

ember-cli-qunit 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 🌴

[Feature request] Custom classnames

Feature request: Add a way to apply custom classnames on the container with position: fixed;. It is often useful to use its own classnames inside an element to keep a low CSS specificity.

For example:

.my-container {
  z-index: 1000;
}
{{#sticky-element containerClassName="my-container"}}
  <h2>Sticky Element</h2>
{{/sticky-element}}

Safari iOS scrollEnd

Hi, is there anywhere way to work around the issue where Safari doesn't repaint until a scroll ends?

This causes issues when trying to use this add-on for sticky navigation items - since a user may scroll to a position and only after inertial scrolling ends does the sticky element appear.

Support re-sticking to top on scroll up after sticking to bottom

When a bottom=0 param is provided so that the element sticks to the bottom of the container, once it's stuck to the bottom it stays there until you scroll back above the container then back down again.

I was expecting the position: sticky behaviour to be reapplied when scrolling up past the stuck element so that it's always sitting in the top-left for example.

I made a quick screen recording as it's probably easier to explain that way!
https://youtu.be/yawUVyJmV90

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

The devDependency eslint-plugin-ember was updated from 5.2.0 to 5.3.0.

🚨 View failing branch.

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

eslint-plugin-ember 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 🌴

Update to ember-in-viewport 3.1

Investigate errors caused by updating to 3.1.0, see #61.

updateIntersectionObserver() needs to be fixed (which is using some private APIs 😔), but that alone does not fix all errors...

ember-in-viewport 3.0.3 = double-modification in single-render error

I tried upgrading to the new ember-in-viewport 3.0.3 release which has some nice perf improvements when multiple in-viewport elements are on a single screen. Unfortunately the upgrade causes a double-modification from ember-sticky-element error in our app.

Error: Assertion Failed: You modified "style" twice on <ghost-admin@component:sticky-element::ember1221> in a single render. It was rendered in "component:sticky-element" and modified in "component:sticky-element/trigger". This was unreliable and slow in Ember 1.x and is no longer supported. See https://github.com/emberjs/ember.js/issues/13948 for more details.


assert | @ | index.js:146
-- | -- | --
  | assertNotRendered | @ | ember-metal.js:1276
  | notifyPropertyChange | @ | ember-metal.js:1560
  | (anonymous) | @ | ember-metal.js:1609
  | _forEachIn | @ | ember-metal.js:2897
  | forEachInDeps | @ | ember-metal.js:2870
  | iterDeps | @ | ember-metal.js:1598
  | dependentKeysDidChange | @ | ember-metal.js:1578
  | notifyPropertyChange | @ | ember-metal.js:1543
  | (anonymous) | @ | ember-metal.js:1609
  | _forEachIn | @ | ember-metal.js:2897
  | forEachInDeps | @ | ember-metal.js:2870
  | iterDeps | @ | ember-metal.js:1598
  | dependentKeysDidChange | @ | ember-metal.js:1578
  | notifyPropertyChange | @ | ember-metal.js:1543
  | (anonymous) | @ | ember-metal.js:1609
  | _forEachIn | @ | ember-metal.js:2897
  | forEachInDeps | @ | ember-metal.js:2870
  | iterDeps | @ | ember-metal.js:1598
  | dependentKeysDidChange | @ | ember-metal.js:1578
  | notifyPropertyChange | @ | ember-metal.js:1543
  | set | @ | ember-metal.js:3575
  | set | @ | observable.js:104
  | updatePosition | @ | sticky-element.js:292
  | parentBottomExited | @ | sticky-element.js:326
  | _join | @ | backburner.js:741
  | join | @ | backburner.js:477
  | run.join | @ | ember-metal.js:456
  | (anonymous) | @ | ember-glimmer.js:973
  | exports.flaggedInstrument | @ | ember-metal.js:4580
  | (anonymous) | @ | ember-glimmer.js:972
  | didExitViewport | @ | trigger.js:62
  | trigger | @ | core_view.js:62
  | superWrapper | @ | ember-utils.js:428
  | _triggerDidAccessViewport | @ | in-viewport.js:299
  | _triggerDidAccessViewport | @ | trigger.js:135
  | superWrapper | @ | ember-utils.js:428
  | _setViewportEntered | @ | in-viewport.js:209
  | updateIntersectionObserver | @ | trigger.js:95
  | updateViewportOptions | @ | trigger.js:83
  | (anonymous) | @ | trigger.js:110
  | sendEvent | @ | ember-metal.js:246
  | flush | @ | ember-metal.js:1190
  | endPropertyChanges | @ | ember-metal.js:1643
  | changeProperties | @ | ember-metal.js:1667
  | setProperties | @ | ember-metal.js:5542
  | setProperties | @ | observable.js:121
  | update | @ | ember-glimmer.js:4296
  | evaluate | @ | runtime.js:1907
  | execute | @ | runtime.js:4192
  | rerender | @ | runtime.js:4491
  | _this27.render | @ | ember-glimmer.js:4558
  | runInTransaction | @ | ember-metal.js:1231
  | _renderRoots | @ | ember-glimmer.js:4819
  | _renderRootsTransaction | @ | ember-glimmer.js:4851
  | _revalidate | @ | ember-glimmer.js:4891
  | invoke | @ | backburner.js:205
  | flush | @ | backburner.js:125
  | flush | @ | backburner.js:278
  | end | @ | backburner.js:410
  | _run | @ | backburner.js:760
  | _join | @ | backburner.js:736
  | join | @ | backburner.js:477
  | loopEnd | @ | ember-glimmer.js:4666
  | _trigger | @ | backburner.js:819
  | end | @ | backburner.js:423
  | _run | @ | backburner.js:760
  | _join | @ | backburner.js:736
  | join | @ | backburner.js:477
  | loopEnd | @ | ember-glimmer.js:4666
  | _trigger | @ | backburner.js:819
  | end | @ | backburner.js:423
  | _run | @ | backburner.js:760
  | _join | @ | backburner.js:736
  | join | @ | backburner.js:477
  | run.join | @ | ember-metal.js:456
  | jqXHR.done | @ | ajax-request.js:232
  | fire | @ | jquery.js:3268
  | fireWith | @ | jquery.js:3398
  | done | @ | jquery.js:9305
  | (anonymous) | @ | jquery.js:9548
  | load (async) |   |  
  | send | @ | jquery.js:9567
  | ajax | @ | jquery.js:9206
  | _makeRequest | @ | ajax-request.js:223
  | _makeRequest | @ | ajax.js:183
  | superWrapper | @ | ember-utils.js:428
  | request | @ | ajax-request.js:175
  | ajax | @ | ajax-support.js:37
  | query | @ | base.js:37
  | query | @ | embedded-relation-adapter.js:29
  | superWrapper | @ | ember-utils.js:428
  | _query | @ | -private.js:8817
  | _query | @ | -private.js:10971
  | query | @ | -private.js:10958
  | model | @ | edit.js:16
  | deserialize | @ | route.js:951
  | applyHook | @ | router.js:211
  | runSharedModelHook | @ | router.js:662
  | getModel | @ | router.js:896
  | tryCatcher | @ | rsvp.js:200
  | invokeCallback | @ | rsvp.js:372
  | publish | @ | rsvp.js:358
  | (anonymous) | @ | rsvp.js:14
  | invoke | @ | backburner.js:205
  | flush | @ | backburner.js:125
  | flush | @ | backburner.js:278
  | end | @ | backburner.js:410
  | _runExpiredTimers | @ | backburner.js:831
  | Backburner._boundRunExpiredTimers | @ | backburner.js:368
  | setTimeout (async) |   |  
  | Backburner.platform.setTimeout | @ | backburner.js:354
  | _installTimerTimeout | @ | backburner.js:876
  | _reinstallTimerTimeout | @ | backburner.js:858
  | _setTimeout | @ | backburner.js:786
  | later | @ | backburner.js:566
  | run.later | @ | ember-metal.js:681
  | scheduledSendTree | @ | VM955:4659
  | invoke | @ | backburner.js:205
  | flush | @ | backburner.js:125
  | flush | @ | backburner.js:278
  | end | @ | backburner.js:410
  | _run | @ | backburner.js:760
  | run | @ | backburner.js:468
  | run | @ | ember-metal.js:408
  | wrap | @ | VM955:3526
  | messageReceived | @ | VM955:3497
  | get.onMessageReceived.message | @ | VM955:3491
  | get.forEach.callback | @ | VM955:127
  | _messageReceived | @ | VM955:126
  | run | @ | VM955:347
  | _run | @ | backburner.js:758
  | run | @ | backburner.js:468
  | run | @ | ember-metal.js:408
  | chromePort.addEventListener.event | @ | VM955:346

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on all 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 we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Once you have installed CI on this repository, you’ll need to re-trigger Greenkeeper’s initial Pull Request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper integration’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.

0.1.4 broke in ember-cli 2.14.2

In my package.json, I had "ember-sticky-element": "^0.1.3". When I deployed it, I wasn't using a shrinkwrapped json file or yarn and the deploy process used ember-sticky-element 0.1.4. My app then broken with the error: Error sticky-element not found, and the catch-all block handler.... After I fixed the version to 0.1.3, things worked again.

Not sure what's going on, but it seems something about the change from 0.1.3 to 0.1.4 caused things to break. Sorry I don't have anything more concrete!

An in-range update of ember-cli-github-pages is breaking the build 🚨

The devDependency ember-cli-github-pages was updated from 0.2.0 to 0.2.1.

🚨 View failing branch.

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

ember-cli-github-pages 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).

Commits

The new version differs by 6 commits.

  • 0e03f72 chore(release): 0.2.1
  • 29e16f9 chore: add release script
  • bbef083 chore: remove bower and update lock files
  • 9a8aa68 fix: update all deps via ember-cli-update
  • f6eef41 chore: updatelock file
  • 820b462 fix: Split git commands to multiple calls to runCommand (#67)

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 🌴

Responsive stickyness?

Hi,

I was looking into e-sticky-element but it doens't support reponsive sticky elements am I right?

Could be a awesome feature for the future..

An in-range update of ember-source-channel-url is breaking the build 🚨

The devDependency ember-source-channel-url was updated from 1.1.0 to 1.2.0.

🚨 View failing branch.

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

ember-source-channel-url 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 Release 1.2.0
  • Print only the url when being piped/scripted. (#65) (aaaa70a)
  • Print only the url when being piped/scripted. (569cd10)
  • Ensure any trailing whitespace in package.json is preserved. (#64) (da4d191)
  • Add --write to README (21e9cf6)
  • Ensure any trailing whitespace in package.json is preserved. (d661a2c)
  • Add testing for Node 12. (#63) (7109a8f)
  • Add ability to update package.json automatically. (#62) (09ad315)
  • Add testing for Node 12. (66e8c76)
  • Add ability to update package.json automatically. (cd73756)
  • Build(deps-dev): Bump prettier from 1.17.0 to 1.17.1 (47bc549)
  • Build(deps-dev): Bump eslint-plugin-prettier from 3.0.1 to 3.1.0 (6e4f924)
  • Build(deps-dev): Bump eslint-config-prettier from 4.1.0 to 4.2.0 (dc4958d)
  • Build(deps-dev): Bump prettier from 1.16.4 to 1.17.0 (6a72e16)
  • Build(deps-dev): Bump eslint from 5.15.3 to 5.16.0 (df01a27)
  • Build(deps-dev): Bump eslint from 5.15.2 to 5.15.3 (7709622)
  • Build(deps-dev): Bump eslint from 5.15.1 to 5.15.2 (ac576b9)
  • Build(deps-dev): Bump eslint from 5.15.0 to 5.15.1 (d07f9f4)
  • Build(deps-dev): Bump get-port from 4.1.0 to 4.2.0 (e511f1c)
  • Build(deps-dev): Bump eslint from 5.14.1 to 5.15.0 (ef45eb7)
  • Build(deps-dev): Bump eslint-config-prettier from 4.0.0 to 4.1.0 (19aba04)
  • Build(deps-dev): Bump qunit from 2.9.1 to 2.9.2 (372c451)
  • Build(deps-dev): Bump eslint from 5.14.0 to 5.14.1 (eb9c5bb)
  • Build(deps-dev): Bump eslint from 5.13.0 to 5.14.0 (0391dcd)
  • Build(deps-dev): Bump prettier from 1.16.3 to 1.16.4 (815f4f3)
  • Build(deps-dev): Bump eslint from 5.12.1 to 5.13.0 (e3deeff)
  • Build(deps-dev): Bump prettier from 1.16.1 to 1.16.3 (94f2738)
  • Build(deps-dev): Bump eslint-config-prettier from 3.6.0 to 4.0.0 (#41) (800e57c)
  • Build(deps-dev): Bump prettier from 1.16.0 to 1.16.1 (e8cefee)
  • Build(deps-dev): Bump eslint from 5.12.0 to 5.12.1 (230d407)
  • Build(deps-dev): Bump prettier from 1.15.3 to 1.16.0 (faa82d8)
  • Build(deps-dev): Bump eslint-config-prettier from 3.5.0 to 3.6.0 (74e9d14)
  • Build(deps-dev): Bump eslint-config-prettier from 3.4.0 to 3.5.0 (4838487)
  • Build(deps-dev): Bump eslint-config-prettier from 3.3.0 to 3.4.0 (01e30d0)
  • Build(deps-dev): Bump qunit from 2.8.0 to 2.9.1 (#34) (424592e)
  • Build(deps-dev): Bump eslint-plugin-node from 8.0.0 to 8.0.1 (#32) (b4e99cf)
  • Build(deps-dev): Bump eslint from 5.11.1 to 5.12.0 (#33) (6bf82eb)
  • Build(deps-dev): Bump eslint-plugin-prettier from 3.0.0 to 3.0.1 (#30) (8744eb9)
  • Build(deps-dev): Bump eslint from 5.11.0 to 5.11.1 (#29) (446f295)
  • Bump eslint from 5.10.0 to 5.11.0 (#28) (7b0373e)
  • Bump get-port from 4.0.0 to 4.1.0 (#27) (a12af84)
  • Bump eslint-plugin-node from 6.0.1 to 8.0.0 (#25) (92358df)
  • Bump got from 8.0.1 to 8.3.2 (#26) (a92191c)
  • Bump eslint-plugin-prettier from 2.7.0 to 3.0.0 (#24) (27a36cc)
  • Bump eslint-config-prettier from 2.9.0 to 3.3.0 (#20) (4861277)
  • Bump eslint from 4.15.0 to 5.10.0 (#19) (79787b8)
  • Bump eslint-plugin-prettier from 2.4.0 to 2.7.0 (#21) (f37955d)
  • Bump execa from 0.10.0 to 1.0.0 (#23) (b8ee1dd)
  • Bump get-port from 3.2.0 to 4.0.0 (#13) (acad1fd)
  • Bump qunit from 2.5.0 to 2.8.0 (#8) (5113ba0)
  • Merge pull request #18 from Turbo87/node-4 (bcdd4c9)
  • package.json: Update Node.js support range (f6d3492)
  • CI: Add Node 10 to test matrix (544b7d5)
  • CI: Drop Node 9 from test matrix (70e39b9)
  • CI: Drop Node 4 from test matrix (edab98f)
  • [Security] Bump lodash from 4.17.4 to 4.17.11 (#6) (c5d19ec)
  • [Security] Bump mixin-deep from 1.3.0 to 1.3.1 (#12) (da40a84)
  • [Security] Bump atob from 2.0.3 to 2.1.2 (#14) (4deaeba)
  • Bump eslint-plugin-node from 5.2.1 to 6.0.1 (#10) (d3cf700)
  • Bump rsvp from 4.7.0 to 4.8.4 (#7) (3de163d)
  • Bump prettier from 1.10.2 to 1.15.3 (#17) (b0449db)
  • Merge pull request #16 from Turbo87/sane (336df40)
  • Pin qunit dependency to v2.6.x (d77b1af)
Commits

The new version differs by 63 commits.

  • 0461822 Release 1.2.0
  • aaaa70a Print only the url when being piped/scripted. (#65)
  • 569cd10 Print only the url when being piped/scripted.
  • da4d191 Ensure any trailing whitespace in package.json is preserved. (#64)
  • 21e9cf6 Add --write to README
  • d661a2c Ensure any trailing whitespace in package.json is preserved.
  • 7109a8f Add testing for Node 12. (#63)
  • 09ad315 Add ability to update package.json automatically. (#62)
  • 66e8c76 Add testing for Node 12.
  • cd73756 Add ability to update package.json automatically.
  • 47bc549 Build(deps-dev): Bump prettier from 1.17.0 to 1.17.1
  • 6e4f924 Build(deps-dev): Bump eslint-plugin-prettier from 3.0.1 to 3.1.0
  • dc4958d Build(deps-dev): Bump eslint-config-prettier from 4.1.0 to 4.2.0
  • 6a72e16 Build(deps-dev): Bump prettier from 1.16.4 to 1.17.0
  • df01a27 Build(deps-dev): Bump eslint from 5.15.3 to 5.16.0

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

How to avoid "Assertion Failed: calling set on destroyed object" errors in testing?

I just started using this addon today and noticed a few new global test failures...

Chrome 65.0 - Global error: Uncaught Error: Assertion Failed: calling set on destroyed object
<desktop-frontend@component:sticky-element::ember13313>.parentTop = top at http://localhost:4203/assets/vendor.js, line 31275

Does this indicate a problem with my app specifically? I'm on Ember 2.18.

An in-range update of ember-cli-htmlbars-inline-precompile is breaking the build 🚨

The devDependency ember-cli-htmlbars-inline-precompile was updated from 1.0.3 to 1.0.4.

🚨 View failing branch.

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

ember-cli-htmlbars-inline-precompile 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 🌴

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.