Update dependency html-validate to v9 - autoclosed #262
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.
This PR contains the following updates:
8.29.0
->9.1.0
Release Notes
html-validate/html-validate (html-validate)
v9.1.0
Compare Source
Features
Bug Fixes
toMatchCodeframe
(3c29ad5)v9.0.1
Compare Source
Bug Fixes
validateMultipleFiles
incorrectly using sync API (0c26918)v9.0.0
Compare Source
ESM support has finally landed in HTML-Validate V9!
.htmlvalidate.mjs
or when"type"
is"module"
inpackage.json
).This release is primarly breaking for API uses but some configuration changes might be required (see below).
For API users the TL;DR version is most functions can return a
Promise
so make sure toawait
it.⚠ BREAKING CHANGES
meta: The deprecated metadata property expressions have been removed
and can be replaced with callback functions. This gives greater control for the
metadata author, provides better IDE support and is more reusable when querying
the metadata directly.
api:
Config.merge(..)
will return aPromise
when used with anasync loader or resolver.
config: This change affects all users. The following deprecated
configuration presets has been removed:
htmlvalidate:recommended
htmlvalidate:document
html-validate:a17y
cli: CLI uses ESM (with
esmResolver
). For most part this shouldn'taffect anything but in some cases you might need slight configuration
migration. See Migration Guide for details.
refactor(cli): use ESM in CLI
tag:open
andtag:close
events has beenremoved, use
tag:begin
andtag:end
instead.Config.resolve()
method can return aPromise
if anyunderlying loader or resolver has returned a
Promise
.It is recommended to assume it returns a
Promise
and alwaysawait
theresult:
If you need synchronous code ensure the configuration, the loader and the
resolver all returns synchronous results, e.g. the
staticResolver
withsynchronous code.
HtmlValidate.getConfigurationSchema()
method is now asyncand returns a
Promise
. If you use this method you need to await the result:optionally return a
Promise
. If you are usingtest-utils
to write unit testsyou must now resolve the promise.
This is no matter if your transformer is actually async or not.
CLI.isIgnored(..)
method has been removed from the publicAPI. There is no replacement. If you need this method open an issue describing
the use-case.
CLI
class most methods are now async andreturns
Promise
. There is no synchronous version of these API calls.Config.fromFile(..)
andConfig.fromObject(..)
will return aPromise when used with an async loader or resolver.
ConfigLoader
methods can optionally return aPromise
forasync operation. For most use-cases this will not require any changes.
ConfigLoader.globalConfig
property has been replaced withConfigLoader.getGlobalConfig()
(async) andConfigLoader.getGlobalConfigSync()
(sync).Config.init()
method has beenremoved.
Remove any calls to the method:
const config = Config.fromObject({ /* ... */ }); -config.init();
Features
CLI.isIgnored()
made private (9e3679a)CLI
methods async and return Promise (677c73e)Config.fromFile
andConfig.fromObject
can returnPromise
(b126361)Config.merge(..)
can returnPromise
(cccb313)Config.resolve()
can returnPromise
(09159f3)ConfigLoader
s can optionally returnPromise
for async operation (6041581)FileSystemConfigLoader
usesesmResolver
by default (dd4cfb1)HtmlValidate.getConfigurationSchema()
returns promise (f10ec1a)esmResolver
usingimport(..)
(available for both nodejs and browser) (81b4777), closes #230Config.init()
(0bd8ab7)tag:open
andtag:close
events (88ac65e)ConfigLoader.globalConfig
withConfigLoader.getGlobalConfig()
(a64935a)Promise
for async operation (fe3c6a6)Promise
for async operation (823da19)esmResolver
) (3e4759e).htmlvalidate.mjs
configuration files (0ffd9b5), closes #125Configuration
📅 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.
This PR was generated by Mend Renovate. View the repository job log.