Update metro-core 0.80.6 → 0.80.9 (minor)

[depfu]

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?

✳️ metro-core (0.80.6 → 0.80.9) · Repo · Changelog

Release Notes

0.80.9

• [Feature]: Allow configuring HttpStore's read and write paths separately. (3e647a6 by @GijsWeterings)
• [Feature]: Add additionalSuccessStatuses option to HttpStore. (f8f7d55 by @motiz88)
• [Fix]: Prevent cache write errors from killing the server, log them to reporter instead. (15815d0 by @motiz88)
• [Fix]: Node crawler (non-Watchman) returns non-deterministic partial results on silent directory read errors. (105e222 by @robhogan)
• [Fix]: Dedupe Watchman crawl warnings correctly. (#1260 by @EvanBacon)
• [Fix]: Improve error message for invalid asset paths. (#1267 by @fredrikburmester)

NOTE: Experimental features are not covered by semver and can change at any time.

• [Experimental]: Add unstable_renameRequire transformer option. (#1230 by @EvanBacon)

Full Changelog: v0.80.8...v0.80.9

0.80.8

• [Fix]: Guard against invalid symbolication in Chrome DevTools by terminating each module's source map with a null mapping (96c6b89 by @motiz88)

NOTE: Experimental features are not covered by semver and can change at any time.

• [Experimental]: Package exports resolution: Fix implicit default condition to be null for subpath patterns (edge case) (#1239 by @jbroma)

Full Changelog: v0.80.7...v0.80.8

0.80.7

• [Fix]: Fix startup time regression when using Watchman on Windows with a warm cache. (#1231 by @robhogan)

Full Changelog: v0.80.6...v0.80.7

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 34 commits:

• Publish 0.80.9
• fix: template literal syntax in error handling for asset file paths (#1267)
• fix metro-file-map spamming watchman warnings (#1260)
• Node file crawler - warn and keep going on unreadable directories
• Deploy 0.235.1 to xplat
• Pre-suppress unsafe string key access errors in xplat/js
• Deploy 0.234.0 to xplat
• Deploy v0.233.0 to xplat
• Optionally log HTTP responses in HttpStore errors
• Allow configuring additional success statuses in HttpStore
• Prepare HttpStore for separate configurability for reads and writes
• Add SerializedEvent type to JsonReporter
• Logger: Don't unnecessarily overwrite log_entry_label with action_name
• Log cache I/O errors to `reporter` without killing the server
• feat: add `unstable_renameRequire` to allow disabling the require rename transform (#1230)
• refactor(metro-resolver): more descriptive assertions in should resolve exports target directly tests (#1240)
• Release 0.80.8
• Add changelog guidance to PR template
• fix(metro-resolver): package exports restricted paths (#1239)
• Deploy 0.232.0 to xplat
• Fix some cyclic types
• Terminate module source maps with a null mapping
• Release 0.80.7
• eslint: Update @typescript-eslint monorepo to v7 & eslint-plugin-jest to v27
• Update eslint to `^8.57.0`
• Deploy 0.231.0 to xplat
• Deploy 0.230.0 to xplat
• Fix regression in incremental Watchman queries on Windows (#1231)
• Update hermes-parser and related packages in fbsource to 0.20.1
• Update hermes-parser and related packages in fbsource to 0.20.0
• Remove `casting_syntax=both` option from flowconfigs now that it is the default
• Deploy 0.229.2 to xplat
• Update hermes-parser and related packages in fbsource to 0.19.2
• Deploy 0.229.0 to xplat

---

👉 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

@​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 cancel merge

Cancels automatic merging of this PR

@​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)