Update nise to 1.4.1

[tzrh]

Purpose (TL;DR) - mandatory

It would be useful to have sinonjs/nise#45 included.

How to verify - mandatory

1. Check out this branch
2. npm install
3. npm test

Checklist for author

• npm run lint passes
• References to standard library functions are cached.

[coveralls]

Pull Request Test Coverage Report for Build 2589

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 95.24%

---

Totals
Change from base Build 2584:	0.0%
Covered Lines:	1965
Relevant Lines:	2019

---

💛 - Coveralls

[mroderick]

@tzrh when you install sinon from NPM it uses the latest nise, because of the caret range: https://docs.npmjs.com/misc/semver#caret-ranges-123-025-004

$ npm install sinon@latest --save-dev

+ sinon@6.1.3
added 15 packages from 330 contributors and audited 18 packages in 3.072s
found 0 vulnerabilities

$ npm ls nise
tmp-1859@1.0.0 /Users/mroderick/tmp-1859
└─┬ sinon@6.1.3
  └── nise@1.4.2

Perhaps it is frozen in your package-lock.json / yarn.lock?

[tzrh]

I missed that, thanks!

[tzrh]

@mroderick Is it possible that nise hasn't been updated in the packaged sinon build, as happened with #1656? In http://sinonjs.org/releases/sinon-6.0.1.js, I don't see these lines.

Edit: Added this to #1861.

[mroderick]

@tzrh I think you're correct!

Do you have a proposal for how we can ensure that the packaged build is done with the latest versions?

[tzrh]

Adding npm update to https://github.com/sinonjs/sinon/blob/master/scripts/postversion.sh might make sense. I'm not sure if that's taking that script further away from it's original purpose though.

Edit: A check of the output for npm outdated --parseable would be less invasive.