chore(deps): bump @humanspeak/svelte-markdown from 1.4.5 to 1.8.5 in /paaster

[dependabot]

Bumps @humanspeak/svelte-markdown from 1.4.5 to 1.8.5.

Release notes

Sourced from @​humanspeak/svelte-markdown's releases.

Release v1.8.5

Changes in this Release build(docs): bump docs-kit to 2026.7.6

For more details, see the Pull Request

Release v1.8.4

[!IMPORTANT] This release fixes v1.8.0–v1.8.3, which are deprecated on npm: those versions broke module resolution (Could not resolve "shiki/core") for anyone importing from @humanspeak/svelte-markdown/extensions without the optional shiki peer dependency installed.

If you use the shiki extension, update your import — everything else is unchanged:

- import { createShikiHighlighter, ShikiCode, setShikiHighlighter } from '@humanspeak/svelte-markdown/extensions'
+ import { createShikiHighlighter, ShikiCode, setShikiHighlighter } from '@humanspeak/svelte-markdown/extensions/shiki'

Changes in this Release fix(extensions): drop shiki from the extensions barrel

For more details, see the Pull Request

Release v1.8.3

[!CAUTION] This release is broken and deprecated on npm — use v1.8.4 or later.

Importing anything from @humanspeak/svelte-markdown/extensions (even just markedAlert) fails with Could not resolve "shiki/core" unless the optional shiki peer dependency is installed. The barrel mistakenly re-exported the shiki extension, whose static shiki/core import forces bundlers to resolve shiki for every barrel consumer. Fixed in v1.8.4 (#369).

If you use the shiki extension: after upgrading, change your import from @humanspeak/svelte-markdown/extensions to @humanspeak/svelte-markdown/extensions/shiki. All other barrel exports are unchanged.

Changes in this Release refactor(parser): single identity rule for streaming token reuse

For more details, see the Pull Request

Release v1.8.2

[!CAUTION] This release is broken and deprecated on npm — use v1.8.4 or later.

Importing anything from @humanspeak/svelte-markdown/extensions (even just markedAlert) fails with Could not resolve "shiki/core" unless the optional shiki peer dependency is installed. The barrel mistakenly re-exported the shiki extension, whose static shiki/core import forces bundlers to resolve shiki for every barrel consumer. Fixed in v1.8.4 (#369).

If you use the shiki extension: after upgrading, change your import from @humanspeak/svelte-markdown/extensions to @humanspeak/svelte-markdown/extensions/shiki. All other barrel exports are unchanged.

Changes in this Release refactor(streaming): reset streamTokens by reference replacement

For more details, see the Pull Request

Release v1.8.1

[!CAUTION]

... (truncated)

Commits

• 448e4f8 Bump version to v1.8.5 [skip ci]
• 2a0b000 build(docs): bump docs-kit to 2026.7.6 (#370)
• 721cd59 Bump version to v1.8.4 [skip ci]
• dfc1bb2 fix(extensions): drop shiki from the extensions barrel (#369)
• 36afe81 Bump version to v1.8.3 [skip ci]
• d7f5a03 refactor(parser): single identity rule for streaming token reuse (#368)
• e10bfcc chore(plans): re-baseline plan 011 to e8940c5 after 001/002 landed (#366)
• 1b8d308 test(streaming): extract shared rAF/fake-timer harness across five suites (#367)
• e8940c5 Bump version to v1.8.2 [skip ci]
• 1374551 refactor(streaming): reset streamTokens by reference replacement (#364)
• Additional commits viewable in compare view

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​humanspeak/​svelte-markdown@​1.4.5 ⏵ 1.8.5	+1			+1

View full report

[socket-security]

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		Potential code anomaly (AI signal): npm marked is 74.0% likely to have a medium risk anomaly Notes: No strong evidence of hidden malware (no network access, no credential access, no persistence, and no obvious obfuscated payloads) in this fragment. The primary security concern is design: it executes local configuration files as JavaScript modules via require()/dynamic import based on --config (or default locations in the user’s home). If an attacker can influence which config file is loaded, this becomes an arbitrary code execution risk in the context of the CLI user. Otherwise, it behaves like a standard Markdown-to-HTML CLI with file I/O and stdout output. Confidence: 0.74 Severity: 0.50 From: paaster/package-lock.json → npm/@humanspeak/svelte-markdown@1.8.5 → npm/marked@18.0.9 ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/marked@18.0.9. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report