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
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
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?
✳️ nodemon (2.0.13 → 2.0.22) · Repo
Release Notes
2.0.22
2.0.21
2.0.20
2.0.19
2.0.18
2.0.16
2.0.15
2.0.14
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 70 commits:
Merge branch 'main' of github.com:remy/nodemon
chore: supporters
fix: remove ts mapping if loader present
One more fix
Get rid of spawning shell windows if nodemon is started without console.
Merge branch 'main' of github.com:remy/nodemon
chore: missing supporters
fix: remove ts mapping if loader present
chore: add conventional commit check
One more fix
Get rid of spawning shell windows if nodemon is started without console.
chore: update supporters
chore: + support
chore: supporters
chore: update
chore: update supporters
chore: fix url
chore: supporters
chore: supporters
chore: supporters
Merge branch 'main' of github.com:remy/nodemon
chore: update supporters
docs: add workaround for inspect problem to faq.md
fix: remove postinstall script
chore: supports
chore: supporters
chore: supporters
chore: supporters update
chore: supporters update
chore: add unused files to .npmignore (#2055)
docs: added link on banner (#1944)
docs: add important note about ignore rules
chore: supporters
chore: update supportors
chore: add supporter
chore: supporters
chore: supporter alt support
chore: add supporters
chore: fix supporter image sizes
chore: supporters
chore: upgrade minimatch dependency to 3.1.2 (#2052)
docs: Update documentation about support for unix globbing (#2016)
docs: Update index.html (#2036)
fix: Replace update notifier with simplified deps (#2033)
docs: fix bug_report.md (#2032)
fix: revert update-notifier forcing esm
fix: update packge-lock
fix: bump update-notifier to v6.0.0 (#2029)
chore: update supporters
chore: add supporter
fix: support windows by using path.delimiter
docs: add syntax highlighting to sample-nodemon.md (#1982) (#2004)
docs: Unified Node.js capitalization (#1986)
docs: add note to faq with example showing how to watch any file extension (#1931)
chore: update sponsors
chore: add supporters
chore: update supporters
chore: supporters
chore: updating supporters
Merge branch 'main' of github.com:remy/nodemon
chore: update supporters
ci(release): workflow uses 'npm' cache (#1933)
ci(node.js): workflow uses 'npm' cache (#1934)
docs: Fix typo in faq.md (#1950)
fix: bump prod dep versions
chore: update supporters
fix: add windows signals SIGUSR2 & SIGUSR1 to terminate the process (#1938)
docs: Fix typo in faq.md
chore: update supporters
chore: add supporter
👉 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