Bump grunt-contrib-jasmine from 1.0.3 to 2.0.3

[dependabot-preview]

Bumps grunt-contrib-jasmine from 1.0.3 to 2.0.3.

Changelog

Sourced from grunt-contrib-jasmine's changelog.

v2.0.3:
date: 2018-11-14
changes:
- Fix security deps: lodash
- Build only should pass if the buildSpecrunner runs without error
v2.0.2:
date: 2018-08-13
changes:
- Fix noSandbox option.
- Fix startTime, and timing issues.

v2.0.1:
date: 2018-05-31
changes:
- Use the grunt current working directory to find the jasmine core.
- Implement options.version.
- Dependency updates.

v2.0.0:
date: 2018-05-19
changes:
- Switch from PhantomJS to Chrome Headless via Puppeteer

v1.1.0:
date: 2017-01-12
changes:
- adds tempDir option.
- locks jasmine version

Commits

• 201bb2a Release v2.0.3
• 9b18221 Upgrade npm dependencies
• d0e2572 fix: build only should pass if the buildSpecrunner runs without error
• 74855ed Update dependencies
• d65dd20 v2.0.2
• d7f652f Fix typo
• 55a5f1f Wait for spec runner before larunching browser
• 408a233 Set the startTime before calling sendMessage
• a30f731 Create new optional 'noSandbox' option to launching Puppeteer with no-sandbox...
• a88f31b Launching Puppeteer with no-sandbox arg.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.

[jywarren]

@dependabot rebase

[jywarren]

OK, looks like maybe a breaking change in how Jasmine tasks are formatted?

0.86s$ grunt jasmine
Loading "jasmine.js" tasks...ERROR
>> SyntaxError: missing ) after argument list

[jywarren]

@dependabot rebase

[jywarren]

Some guidance on upgrading to Jasmine 2.0 here:

• Upgrade to Jasmine 2.2.0 CesiumGS/cesium#2495
• Upgrade to jasmine 2.0.0 searls/jasmine-maven-plugin#192

Oh, oops. Here we're only updateing grunt-contrib-jasmine not jasmine itself. Disregard.

[jywarren]

https://github.com/gruntjs/grunt-contrib-jasmine

[jywarren]

This now uses Chrome Headless, which may be an issue? https://github.com/GoogleChrome/puppeteer/blob/master/docs/troubleshooting.md#running-puppeteer-on-travis-ci

[jywarren]

Also seeing:

> node install.js
/home/travis/build/publiclab/PublicLab.Editor/node_modules/puppeteer/install.js:86
let progressBar = null;
^^^
SyntaxError: Block-scoped declarations (let, const, function, class) not yet supported outside strict mode

Maybe we need to include puppeteer in our .travis.yml configs?

[jywarren]

OK - lots of useful errors now. Deprecating Node v5 and v6, the other Travis tests now return more useful errors.

[jywarren]

Mostly prob related to:

     Error: Fixture could not be loaded: spec/javascripts/fixtures/index.html (status: error, message: Failed to execute 'send' on 'XMLHttpRequest': Failed to load 'file:///home/travis/build/publiclab/PublicLab.Editor/spec/javascripts/fixtures/index.html?_=1546383838422'.) (1)

[jywarren]

@rexagod I've addressed a LOT of the dependabot updates and am looking to fix this one before publishing a new patch level update to NPM (addressing much of #195 I hope) -- would you have any time to take a look here to see what's going on? Thank you!!!

[rexagod]

@jywarren There are a number of issues (this, this and many more) regarding this particular package all over the internet (including those over at the inline-md-editor). I mean, sure, we can continue to debug or wait for the devs at grunt to come up with something, or maybe, if you're still interested in that gulp/webpack idea, we can stop spending our time here and consider that instead.

Both approaches are fine by me, but I was just concerned about the fact that this has stalled us for quite some time now, and would like to know your thoughts on the same.

[jywarren]

Hmmmm. I hear you. How much work would a Gulp refactor be? I worry if it's a big lift.

…

On Thu, Jan 24, 2019 at 9:24 PM Pranshu Srivastava ***@***.***> wrote: @jywarren <https://github.com/jywarren> There are a number of issues (this <gruntjs/grunt-contrib-jasmine#295>, this <gruntjs/grunt-contrib-jasmine#266> and many more) regarding this particular package all over the internet (not to mention those over at the inline-md-editor <publiclab/inline-markdown-editor#29>). I mean, sure, we can continue to debug or wait for the devs at grunt to come up with something, or maybe, if you're still interested in that gulp idea, we can stop spending our time here and consider that instead. Both approaches are fine by me, but I was just concerned about the fact that this has stalled us for quite some time now, and would like to know your thoughts on the same. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#168 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJ0kZTHO_9SARMKCavWGS8REO5JZ4ks5vGmq_gaJpZM4ZFi_f> .

[dependabot-preview]

A newer version of grunt-contrib-jasmine exists, but since this PR has been edited by someone other than Dependabot I haven't updated it. You'll get a PR for the updated version as normal once this PR is merged.