Repository navigation
Update dependency prettier-plugin-toml to v4 - #678
Merged
Merged
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.
This PR contains the following updates:
3.0.2→4.1.0Release Notes
un-ts/prettier (prettier-plugin-toml)
v4.1.0Compare Source
Minor Changes
#535
4ad8ffeThanks @JounQin! - feat(prettier-plugin-toml): load tombi throughtombittombitwraps the sametombi-libcrate and keeps configuration discovery andmerging in Rust, so the plugin no longer ships
smol-tomlor a JavaScriptdiscovery/caching layer. Prettier's resolved options — including its defaults —
are passed as
overrideConfig; tombi discovers the project's owntombi.toml(or
[tool.tombi]inpyproject.toml) and the user/system configurations.Precedence change: Prettier's core options (
printWidth,tabWidth,useTabs,singleQuote,bracketSpacing) always take precedence over a discoveredtombi.toml. The plugin's own options no longer declare Prettier defaults, sowhen they are not set the discovered configuration (or Tombi's default)
decides; explicitly set options still override it. The discovered
configuration's
[[overrides]]are applied by Tombi last.toml-versionfollows the same rule because it decides how the source is parsed. Formatting a string without a
filepathnow works: configuration discovery starts from the current directory.
Diagnostics now carry a
range, so syntax errors keep rendering their codeframe.
v4.0.0Compare Source
Major Changes
#530
85af9a9Thanks @JounQin! - feat(prettier-plugin-toml)!: migrate from@tombi-toml/wasm-libto@tombi-toml/libTombi is now loaded through its prebuilt native Node.js binding instead of the
WebAssembly build. The WASM loading shim is gone, so the plugin no longer has to
resolve and read the ~6.6 MB
tombi_wasm_bg.wasmfile on first format, and the@dual-bundle/import-meta-resolvedependency is dropped.@tombi-toml/libships platform specific binaries (Linux, macOS and Windowson
x64/arm64, including musl) as optional dependencies.v20.0.0or later is required, matching the engine range declared by@tombi-toml/lib.The exposed options, the configuration discovery and the formatting behaviour
itself are unchanged.
Configuration
📅 Schedule: (in timezone Europe/Zurich)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.