Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Mar 23, 2023

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
babel-watch 7.0.0 -> 7.8.1 age adoption passing confidence

Release Notes

kmagiera/babel-watch (babel-watch)

v7.8.1

Compare Source

Uncategorized
  • #​147 Fix parse freesing on ignored files, catch and rethrow exception…

v7.8.0

Compare Source

Uncategorized
  • Fix: Add error forwarding from babel to stderr (#​143)
  • refactor(compile): use async fns (#​143)
  • feat(actions): add lint and changelog

v7.7.2

Compare Source

v7.7.1

Compare Source

v7.7.0

Compare Source

v7.6.0

Compare Source

v7.5.0: Add --config-file option

Compare Source

Small release to add the --config-file option. #​124

v7.4.1: Fix regression in --extensions

Compare Source

This release fixes #​122, which was caused by an unintended regression in --extensions. Babel's default extensions are always included. We may change this behavior in a major version bump but the behavior in v7 should not change.

v7.4.0: --watch fix and BABEL_WATCH_NODE_OPTIONS

Compare Source

This release fixes two issues:

  • #​98: There wasn't a good way to reliably pass NODE_OPTIONS to the child. If you use NODE_OPTIONS, it will apply both to the babel-watch parent instance and to the child (your code), causing issues with options like --inspect. Therefore, I have added BABEL_WATCH_NODE_OPTIONS, which will be ignored by the parent and passed on to the child like you'd expect. In 99.9% of cases, this is what you want.
  • #​120: It appears the --watch option (i.e. babel-watch --watch interfaces/ app.js) didn't actually do anything very useful. It would add the folder to be watched by chokidar, but because it wasn't required by the application, babel-watch would simply execute no action on a modification. This is not intended so that logic has been removed, and you can now watch arbitrary folders and restart on them.
    • Just be sure to add to --extensions if the files you're watching don't end in .js.
    • If you need to exclude a path, use --exclude. Be careful not to use --ignore, which is instead passed to babel. In a later release I will rename this because it's confusing.
    • See the README for all options.

v7.3.1: NPM package bugfix

Compare Source

An unexpected file made it into the package. This release removes it which greatly decreases the size of the unpacked module.

v7.3.0: 7.3.0: Features!

Compare Source

A few new features in this release:

  • Added --before-restart option. Use to synchronously execute a script between restarts (#​79, #​80, #​102,#​108). For example:
    • babel-watch --before-restart="yarn lint" app.js
  • Added colors to output (and --no-colors option)
    • This changes the default RESTARTING message in favor of something a little less obnoxious. It also prints the files that caused the restart. You can still change it using --message.
  • Added --restart-command, so you can change the default rs<enter> to manually restart. If you set --restart-command=false, the stdin handler is turned off entirely, which is desirable for certain interactive applications. (#​35)
  • Added sourcemaps when --debug/--debug-brk/--inspect/--inspect-brk are present. (#​62, #​118)
    • Added --no-debug-source-maps to disable this behavior, which can be useful if you want to debug the raw transpiled output.

v7.2.0: 7.2.0: New quality-of-life features!

Compare Source

Changes:

  • Fix broken --ignore option, introduced in babel 7 upgrade. (#​106, #​112)
  • Add --clear-console option (#​115)
  • Add debug module. Run with env DEBUG="babel-watch:*" babel-watch [file] to see debug output, including compiled files, ignored files, and init options.
  • Updated README and help messaging.

v7.1.0: 7.1.0: Long-awaited Bugfixes

Compare Source

We finally have publish access again, and have updated babel-watch!

See the release diff for the exact changes.

Highlights:

  • Fix an infinite loop bug when the pipe is closed (#​85, #​46, #​32).
    • If you're using babel-watch and have seen a node process stick at 100% cpu from time to time, this is now fixed if you update!
  • Updated Chokidar from v1 to v3, which improves performance & atomic writes handling (#​97, #​101, #​104, #​105)
  • Debounce app restart to prevent missing cache deletions (#​99)
  • Fix a crash on improper use of Buffer.from() (#​100)

Thanks @​kmagiera for getting publish access into the hands of the community so we can fix these bugs.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot changed the title chore(deps): update dependency babel-watch to v7.7.2 chore(deps): update dependency babel-watch to v7.8.0 Jun 30, 2023
@renovate renovate bot force-pushed the renovate/babel-watch-7.x branch from afce23e to 258c9c7 Compare June 30, 2023 02:27
@renovate renovate bot changed the title chore(deps): update dependency babel-watch to v7.8.0 chore(deps): update dependency babel-watch to v7.8.1 Jul 8, 2023
@renovate renovate bot force-pushed the renovate/babel-watch-7.x branch from 258c9c7 to 297999a Compare July 8, 2023 02:27
@renovate renovate bot force-pushed the renovate/babel-watch-7.x branch from 297999a to 0be1c35 Compare August 12, 2025 00:07
@renovate renovate bot force-pushed the renovate/babel-watch-7.x branch from 0be1c35 to c51b172 Compare September 26, 2025 12:06
@changeset-bot
Copy link

changeset-bot bot commented Sep 26, 2025

⚠️ No Changeset found

Latest commit: c51b172

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant