mdbook/crates/mdbook-markdown/Cargo.toml

[package]
name = "mdbook-markdown"
version = "0.5.0-beta.2"
description = "Markdown processing used in mdBook"
edition.workspace = true
license.workspace = true
repository.workspace = true
rust-version.workspace = true

[dependencies]
pulldown-cmark.workspace = true
regex.workspace = true
tracing.workspace = true

[lints]
workspace = true
Move markdown support to mdbook-markdown This moves all the code responsible for markdown processing to the mdbook-markdown crate. 2025-07-21 15:46:36 -07:00			`[package]`
			`name = "mdbook-markdown"`
Update to 0.5.0-beta.2. I expect this to be the last pre-release before 0.5. 2025-11-07 18:00:52 -08:00			`version = "0.5.0-beta.2"`
Move markdown support to mdbook-markdown This moves all the code responsible for markdown processing to the mdbook-markdown crate. 2025-07-21 15:46:36 -07:00			`description = "Markdown processing used in mdBook"`
			`edition.workspace = true`
			`license.workspace = true`
			`repository.workspace = true`
			`rust-version.workspace = true`

			`[dependencies]`
			`pulldown-cmark.workspace = true`
			`regex.workspace = true`
Switch from log to tracing This switches to using the tracing crate instead of log. Tracing provides a lot of nice features which we can take advantage of moving forward. This also adjusts the output fairly significantly. This includes: - Switched the environment variable from RUST_LOG to MDBOOK_LOG. - Dropped the timestamp. I experimented with various different time displays, but ultimately decided to omit it for now. I don't think I've ever found it to be useful, and it takes up a very significant amount of space. It could potentially be useful for basic profiling, but I think there are other, better mechanisms for that. We could consider leveraging tracing itself for doing some basic profiling (like using something like tracing-chrome). - Dropped the target unless MDBOOK_LOG is set. The target tends to be pretty noisy, and doesn't really convey much information unless you are debugging or otherwise trying to adjust the log output. - Added color. - Slightly reworked the way the error cause trace is displayed. - Slightly changed the way html5ever filtering is done, as well as add handlebars to the list since they both are very noisy. You can override this now by explicitly listing them as targets. I still expect that mdbook will eventually change how it displays things to the console, possibly switching away from tracing and printing things itself. However, that is a larger project for the future. 2025-09-12 06:13:45 -07:00			`tracing.workspace = true`
Move markdown support to mdbook-markdown This moves all the code responsible for markdown processing to the mdbook-markdown crate. 2025-07-21 15:46:36 -07:00
			`[lints]`
			`workspace = true`