Upgrading muggle-string from 0.x to 1.x

Comparison of the public API of muggle-string 0.4.1 and 1.0.0, computed automatically from their TypeScript types. A changed signature is a candidate for a breaking change, not a certainty.

Summary

Removed import paths	0
Removed exports	13
Changed signatures	1
Removed class or interface members	0
Changed class or interface members	0
Newly deprecated	0
Requirement changes (engines, peer dependencies)	1
New exports	12

Removed exports

import	export	kind	Before
`muggle-string`	`track`	function	`<T extends Segment<any>[]>(segments: T, stacks?: StackNode[] \| undefined): [T, StackNode[]]`
`muggle-string`	`create`	function	`(source: string): Segment[]`
`muggle-string`	`Segment`	type	`string \| (T extends typeof NO_DATA_SYMBOL ? [text: string, source: string \| undefined, sourceOffset: number] : [text: string, source: string \| undefined, sourceOffset: number, data: T])`
`muggle-string`	`replace`	function	`<T extends Segment<any>>(segments: T[], pattern: string \| RegExp, ...replacers: (T \| ((match: string) => T))[]): void`
`muggle-string`	`getStack`	function	`(): string`
`muggle-string`	`StackNode`	interface	`interface`
`muggle-string`	`getLength`	function	`(segments: Segment<any>[]): number`
`muggle-string`	`replaceAll`	function	`<T extends Segment<any>>(segments: T[], pattern: RegExp, ...replacers: (T \| ((match: string) => T))[]): void`
`muggle-string`	`offsetStack`	function	`(): void`
`muggle-string`	`setTracking`	function	`(value: boolean): void`
`muggle-string`	`replaceRange`	function	`<T extends Segment<any>>(segments: T[], startOffset: number, endOffset: number, ...newSegments: T[]): void`
`muggle-string`	`resetOffsetStack`	function	`(): void`
`muggle-string`	`replaceSourceRange`	function	`<T extends Segment<any>>(segments: T[], source: string \| undefined, startOffset: number, endOffset: number, ...newSegments: T[]): boolean`

Changed signatures

export	Before	After
`muggle-string · toString`	`<T extends Segment<any>>(segments: T[]): string`

Removed class or interface members

None detected.

Changed class or interface members

None detected.

Newly deprecated

None detected.

Requirement changes (engines, peer dependencies)

	Before	After
`engines.node`	`—`	`^20.19.0 \|\| >=22.12.0`

New exports (12)

import	export	kind
`muggle-string`	`Piece`	type
`muggle-string`	`Source`	interface
`muggle-string`	`SourceMap`	interface
`muggle-string`	`RewriteCode`	type
`muggle-string`	`RewriteSlice`	interface
`muggle-string`	`RewriteOrigin`	type
`muggle-string`	`RewriteWriter`	interface
`muggle-string`	`SourceRewrite`	interface
`muggle-string`	`rewritePieceText`	function
`muggle-string`	`RewriteCutOptions`	type
`muggle-string`	`createSourceRewrite`	function
`muggle-string`	`renderWithSourceMap`	function

Give your AI agent these facts

Vigia is a free MCP server: your coding agent checks versions, breaking changes and vulnerabilities before it writes code. No signup, no API key.

claude mcp add --transport http vigia https://vigia.coredls.cloud/mcp

Add to Cursor Add to VS Code ★ Star on GitHub

Any other MCP client

{ "mcpServers": { "vigia": { "url": "https://vigia.coredls.cloud/mcp" } } }

Agent skill (SKILL.md): tells the agent when to use Vigia · GitHub Action for pull requests

Frequently asked questions

What are the breaking changes when upgrading muggle-string from 0 to 1?

Between muggle-string 0.4.1 and 1.0.0, Vigia found 13 removed exports, 1 changed signatures and 0 removed or changed class or interface members.

What became deprecated in muggle-string 1?

0 exports or members are newly marked as deprecated in muggle-string 1.0.0.

For agents

GET https://vigia.coredls.cloud/v1/packages/npm/muggle-string/upgrade?from=0.4.1&to=1.0.0