Update node-mocks-http 1.8.0 → 1.15.1 (minor) #37
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ node-mocks-http (1.8.0 → 1.15.1) · Repo · Changelog
Release Notes
1.15.1 (from changelog)
1.15.0 (from changelog)
1.14.1 (from changelog)
1.14.0 (from changelog)
1.13.0 (from changelog)
1.12.2 (from changelog)
1.12.1 (from changelog)
1.11.0 (from changelog)
1.10.1 (from changelog)
1.10.0 (from changelog)
1.9.0 (from changelog)
1.8.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 73 commits:
Release 1.15.1
npm audit fix
Allowing `@types/node` v22 (and upgrading it internally) (#305)
Release 1.15.0
More strict check for undefined (#302)
fix: return empty string when send was called with undefined (#298)
add to write and end support of TypedArray (#300)
Disable code coverage comment
Run type check
Update test infra, get rid of gulp (#293)
WIP: enable eslint (#288)
Release 1.14.1
Move express and node types to prod deps (#290)
Enable prettier (#286)
run tests in Node.js v 10
Update links in package.json and readme
Release 1.14.0
Update README.md
Add README paragraph with TypeScript example (#284)
Fix nodejs typing (#281)
Add testing capability in TypeScript (#282)
Release 1.13.0
Bump node version
Request async iterator (#278)
Bump node.js engine version
Bump word-wrap from 1.2.3 to 1.2.4 (#275)
Bump flat and gulp-mocha (#265)
Delete dependency-review.yml
Delete .travis.yml
Create .github/workflows/node.js.yml
Create .github/workflows/dependency-review.yml
Update .travis.yml
Update CONTRIBUTING.md
Update README.md
Update README.md
Release 1.12.2
fix test assertion
run npm audit fix
install all packages from npmjs registry
setHeader should return `this` (#268)
📦️ Upgrade @types/express (#267)
Release 1.12.1
Fix eslint issue
Release 1.12.0
Make it easier to create mocks for the node http library (#259)
mockResponse.end(): added callback triggering once end() logic has run. (#248)
Release 1.11.0
run `npm audit fix`
Fix request.ip and add request.ips (#244)
Add response.attachment() from express (#246)
Add request.getHeader() alias for request.header() (#241)
Release 1.10.1
Fix req.hostname to make it compatible with Express.js (#231)
Bump ini from 1.3.5 to 1.3.7 (#227)
Release 1.10.0
Allow to chain `writeHead()` (#229)
feat: add support for req.hostname (#224)
Release 1.9.0
Remove calls to deprecated Buffer constructors (#221)
New response methods for headers retrieval (#222)
Upgrade (#223)
Implement response.getHeaders() (#217)
Bump node.js versions (#218)
Fix gulp-eslint error due to unexpected token (#219)
Add req.subdomains (#213)
Add socket option to mockRequest (#209)
fix index.d.ts #205 (#206)
Bump handlebars from 4.1.2 to 4.5.3 (#200)
Added support for response.writableEnded and response.writableFinished (#203)
Release 1.8.1
Create stale.yml
Enable res.render() callback argument (#197)
Bump eslint-utils from 1.3.1 to 1.4.3 (#196)
👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * 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 `depfu/`.Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands