Skip to content

Bump vfile-message from 4.0.3 to 4.0.4 - #10

Closed
dependabot[bot] wants to merge 183 commits into
mainfrom
dependabot/npm_and_yarn/vfile-message-4.0.4
Closed

dependabot[bot] wants to merge 183 commits into
mainfrom
dependabot/npm_and_yarn/vfile-message-4.0.4

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 10, 2026

Copy link
Copy Markdown

Bumps vfile-message from 4.0.3 to 4.0.4.

Release notes

Sourced from vfile-message's releases.

4.0.4

Fix

  • eac35ae Fix to not assign defaults through Error.prototype

Types

  • b20e310 Add declaration maps

Full Changelog: vfile/vfile-message@4.0.3...4.0.4

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

jdesrosiers and others added 26 commits October 31, 2026 18:26
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…, for servers that send the wrong Content-Type

mediaTypeByExtension lists the URLs it's for, like GitHub raw URLs, which
are text/plain. It replaces a wrong type as well as a missing one, and is
matched by the URL a response came from after any redirects.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…gument

pointerGet and pointerStep no longer take the document's URI. Every node
has its location, so the message is built from it and made relative with
relativeFileUri. Without a URI, messages said "undefined#", and errors
from Session.step didn't name the document.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… instead of the object's prototype

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Docs follow hyperjump.io's style guide, the Google developer
documentation style guide. Vale checks them through Vale's Claude Code
plugin. The links to the style guide and how to write docs point to
GitHub, so they work without a hyperjump.io checkout.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…etrieval and gets its own headers, and replace options.retrieve with redirects

In Node.js, the HTTP plugin returns a redirect instead of letting fetch
follow it. The session checks where it leads against allowRetrieval
before it's requested, and the plugin picks the headers for that URL.
Before, a header configured for one URL was sent on to wherever a
redirect led, and a refused URL was requested before its response was
refused. Browsers hide where a redirect leads, so there fetch still
follows them.

A plugin for a scheme that maps to another URI, like urn:, returns
Response.redirect instead of calling options.retrieve, so the mapped URI
is checked before it's retrieved too.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… docs

The vocabulary is a Vale package served by the site. Design docs get
spell check and proselint, without the Google style. See
https://github.com/hyperjump-io/hyperjump.io/tree/main/design/style

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… style guide

Sentences are in active voice and say who does what. Task headings and
page titles use the bare verb, option and property tables have a
Description column, and cross-references say "For more information,
see". The parsing examples now type-check: they check a parse's status
before reading its AST, and the reviver's parameters are inferred.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Vale flagged them once it checked design/. The style guide formats
package names as code instead of adding them to the vocabulary.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
What the code used to do, and when it changed, is in git. An old design
that was dropped for a reason is now a rejected alternative with that
reason. Also drop the stale note about linking @hyperjump/uri.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…functions

Session retrieves and parses with the Hyperjump's uriSchemePlugins,
mediaTypePlugins, and accept, instead of private methods it reached
through a static block. The Accept header, a URL's extension, and the
plugin for a Content-Type are functions of the media type plugins, so
they're tested without retrieving anything.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…'t given a base

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
… or pass a lookup function

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…kept in a map by location

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…ments reads them

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
pointerStep is jsonStep, because it takes a key, not a pointer, and
pointerGet is jsonPointerGet.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
step, iter, values, entries, keys, has, and value on Session are
jrefStep, jrefArrayIter, jrefObjectValues, jrefObjectEntries,
jrefObjectKeys, jrefObjectHas, and jrefValue, named for their json*
counterparts. The ones that follow references take the session and
follow them with its public get. Session keeps get and getDocument.

get and the jref* functions return FollowedNode<T>, a node that isn't a
reference, and the jref* functions only take one, so passing a node from
a json* function doesn't type-check until it's narrowed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The reviver option took a JsonNode as its annotations, so a reviver of
JsonTolerantNodes didn't type-check. It now matches fromJson's reviver.

Also: JrefReviver's type parameter is R, like Reviver's. The plugin
docs are on the plugin classes rather than the document types.
JsonParseResult's comments are written inline. The node types call
their annotations A, like JsonNode. jsonValue's overloads are call
signatures, like jrefValue's.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The AST is the value an application transforms, after parsing and
before stringifying, so the parser and toJson don't call code of the
application's. Their types couldn't describe a reviver's result, and
nothing used one except fromJref.

fromJref is fromJson and then a pass over the tree that makes each
object with a string `$ref` a reference. It costs up to 8% on documents
with many references, and fromJson is up to 7% faster without a
reviver (design/benchmarks/reviver-second-pass.md).

fromJson and fromJref take their options third. toJson takes
{ space } in place of its replacer and space arguments, so either hook
could come back as an option.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Harper checks grammar, A11y checks for writing some readers cannot use,
and ai-tells checks for habits of AI-written prose. A [**] section turns
off the rules that are wrong for these docs, and stops the config in
Harper's package from turning it on for every file.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Its rules are lists of words and phrases, and too many of them are usual
in technical writing. Four of its rules were turned off, and others
flagged words these docs need, like "implementation".

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bumps [vfile-message](https://github.com/vfile/vfile-message) from 4.0.3 to 4.0.4.
- [Release notes](https://github.com/vfile/vfile-message/releases)
- [Commits](vfile/vfile-message@4.0.3...4.0.4)

---
updated-dependencies:
- dependency-name: vfile-message
  dependency-version: 4.0.4
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Nov 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant