[backend] Update nodemon: 2.0.13 → 2.0.21 (patch) #210
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
✳️ nodemon (2.0.13 → 2.0.21) · Repo
Release Notes
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 62 commits:
fix: remove ts mapping if loader presentOne more fixGet rid of spawning shell windows if nodemon is started without console.chore: update supporterschore: + supportchore: supporterschore: updatechore: update supporterschore: fix urlchore: supporterschore: supporterschore: supportersMerge branch 'main' of github.com:remy/nodemonchore: update supportersdocs: add workaround for inspect problem to faq.mdfix: remove postinstall scriptchore: supportschore: supporterschore: supporterschore: supporters updatechore: supporters updatechore: add unused files to .npmignore (#2055)docs: added link on banner (#1944)docs: add important note about ignore ruleschore: supporterschore: update supportorschore: add supporterchore: supporterschore: supporter alt supportchore: add supporterschore: fix supporter image sizeschore: supporterschore: 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 esmfix: update packge-lockfix: bump update-notifier to v6.0.0 (#2029)chore: update supporterschore: add supporterfix: support windows by using path.delimiterdocs: 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 sponsorschore: add supporterschore: update supporterschore: supporterschore: updating supportersMerge branch 'main' of github.com:remy/nodemonchore: update supportersci(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 versionschore: update supportersfix: add windows signals SIGUSR2 & SIGUSR1 to terminate the process (#1938)docs: Fix typo in faq.mdchore: update supporterschore: 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:
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