Robin Mehner

Random Drive By (I'm working on all my emails right now and this just popped up): If you use a current npm version and you do have a package-lock.json, then...

@Busteren haven't had the time to test that, will report back (albeit would prefer a proper 1.4 release, but I realize that this might be much more work :))

Btw. this is the error message I'm seeing with #233, when I try to swap in sassc-rails for sass-rails, so that might be related. Just adding more information, still need...

@maldimirov Thanks for looking into this. If I understand you right, you're saying that my schema is not valid per spec? If so, both jsonschema and ajv behave **not** according...

Is there anything we can do to help with getting this released?

Yes, better be clear about the versioning dependencies here. We can use https://docs.npmjs.com/cli/deprecate to deprecate 2.2.0

According to Ember's Node support, we shouldn't drop v4, see https://emberjs.com/blog/2016/09/07/ember-node-lts-support.html

Btw. we've tried to use the command that the quasar plugin for cypress creates, but that one doesn't seem to be compatible to current Quasar versions.

Added a little wait of 5000ms, still no dice. ```diff diff --git a/test/cypress/integration/home/init.spec.js b/test/cypress/integration/home/init.spec.js index 2766544..10f1cc2 100755 --- a/test/cypress/integration/home/init.spec.js +++ b/test/cypress/integration/home/init.spec.js @@ -14,6 +14,10 @@ describe('Landing', () => { cy.get('.q-menu')...

We don't explicitly render, as Cypress is like remote control for Chrome and if we wait, it just sits there and wait and Chrome does its thing, so the tick...