@decimalturn/toml-patch
v0.5.2
Published
Patch, parse, and stringify TOML while preserving comments and formatting.
Downloads
645
Maintainers
Readme
toml-patch
Patch, parse, and stringify TOML while preserving comments and formatting.
Note that this is a maintenance fork of the original toml-patch package. This fork aims at addressing existing issues from the original project, add small to medium sized features and perform dev-dependencies updates. Hopefully, the work done here can go upstream one day if timhall returns, but until then, welcome aboard![^1]
What's New in v0.5.0:
- truncateZeroTimeInDates option: New formatting option to automatically serialize JavaScript Date objects with zero time components (midnight) as date-only values in TOML (
2024-01-15T00:00:00.000Z → 2024-01-15).
What's New in v0.4.0:
- TomlDocument class: A new document-oriented API for stateful TOML manipulation
- TomlFormat class: A class encapsulating all TOML formatting options
- TOML date patching support: You can now safely patch/update a date value inside a TOML document and preserve the original formatting.
Note: The functional API (patch, parse, stringify) remains fully compatible with previous versions. The new TomlDocument class is an additive feature that doesn't break existing code. You can also still use anonymous objects to pass in formatting options. Globally, v0.4.0 shouldn't introduce any breaking changes.
Table of Contents
Installation
toml-patch is dependency-free and can be installed via your favorite package manager.
Example with NPM
$ npm install --save @decimalturn/toml-patchFor browser usage, you can use unpkg:
<script src="https://unpkg.com/@decimalturn/toml-patch"></script>API
toml-patch provides both a functional API for one-time operations and a document-oriented API for more complex workflows.
Functional API
For simple one-time operations, you can use the functional API:
patch(existing, updated, format?)
function patch(
existing: string,
updated: any,
format?: Format,
): stringApplies modifications to a TOML document by comparing an existing TOML string with updated JavaScript data.
This function preserves formatting and comments from the existing TOML document while applying changes from the updated data structure. It performs a diff between the existing and updated data, then strategically applies only the necessary changes to maintain the original document structure as much as possible.
Parameters:
existing: string- The original TOML document as a stringupdated: any- The updated JavaScript object with desired changesformat?: Format- Optional formatting options to apply to new or modified sections
Returns: string - A new TOML string with the changes applied
Patch an existing TOML string with the given updated JS/JSON value, while attempting to retain the format of the existing document, including comments, indentation, and structure.
Example 1
import * as TOML from '@decimalturn/toml-patch';
import { strict as assert } from 'assert';
const existing = `
# This is a TOML document
title = "TOML example"
owner.name = "Bob"
`;
const patched = TOML.patch(existing, {
title: 'TOML example',
owner: {
name: 'Tim'
}
});
assert.strictEqual(
patched,
`
# This is a TOML document
title = "TOML example"
owner.name = "Tim"
`
);Example 2
import * as TOML from '@decimalturn/toml-patch';
import { strict as assert } from 'assert';
const existing = `
# This is a TOML document
title = "TOML example"
owner.name = "Bob"
`;
const jsObject = TOML.parse(existing);
jsObject.owner.name = "Tim";
const patched = TOML.patch(existing, jsObject);
assert.strictEqual(
patched,
`
# This is a TOML document
title = "TOML example"
owner.name = "Tim"
`
);parse(value)
function parse(value: string): anyParses a TOML string into a JavaScript object. The function converts TOML syntax to its JavaScript equivalent. This proceeds in two steps: first, it parses the TOML string into an abstract syntax tree (AST), and then it converts the AST into a JavaScript object.
Parameters:
value: string- The TOML string to parse
Returns: any - The parsed JavaScript object
Example
import * as TOML from '@decimalturn/toml-patch';
import { strict as assert } from 'assert';
const parsed = TOML.parse(`
# This is a TOML document.
title = "TOML Example"
[owner]
name = "Tim"`);
assert.deepStrictEqual(parsed, {
title: 'TOML Example',
owner: {
name: 'Tim'
}
});stringify(value, format?)
function stringify(
value: any,
format?: Format,
): stringConverts a JavaScript object to a TOML string.
Parameters:
value: any- The JavaScript object to stringifyformat?: Format- Optional formatting options for the resulting TOML
Returns: string - The stringified TOML representation
Format Options:
See Formatting Options for more details.
Example
import * as TOML from '@decimalturn/toml-patch';
import { strict as assert } from 'assert';
const toml = TOML.stringify({
title: 'TOML Example',
owner: {
name: 'Tim'
}
});
assert.strictEqual(
toml,
`title = "TOML Example"
[owner]
name = "Tim"`
);TomlDocument Class
The TomlDocument class provides a stateful interface for working with TOML documents. It's ideal when you need to perform multiple operations on the same document.
Constructor
new TomlDocument(tomlString: string)Initializes the TomlDocument with a TOML string, parsing it into an internal representation (AST).
Parameters:
tomlString: string- The TOML string to parse
Basic Usage Example
import * as TOML from '@decimalturn/toml-patch';
const doc = new TOML.TomlDocument(`
# Configuration file
title = "My App"
version = "1.0.0"
[database]
host = "localhost"
port = 5432
`);
console.log(doc.toJsObject);
// Output: { title: "My App", version: "1.0.0", database: { host: "localhost", port: 5432 } }Properties
get toJsObject(): any
get toTomlString(): stringtoJsObject: any- Returns the JavaScript object representation of the TOML documenttoTomlString: string- Returns the TOML string representation (cached for performance)
Methods
patch(updatedObject: any, format?: Format): void
update(tomlString: string): void
overwrite(tomlString: string): voidpatch(updatedObject, format?)
- Applies a patch to the current AST using a modified JS object
- Updates the internal AST while preserving formatting and comments
- Use
toTomlStringgetter to retrieve the updated TOML string - Parameters:
updatedObject: any- The modified JS object to patch withformat?: Format- Optional formatting options
update(tomlString)
- Updates the internal AST by supplying a modified TOML string
- Uses incremental parsing for efficiency (only re-parses changed portions)
- Use
toJsObjectgetter to retrieve the updated JS object representation - Parameters:
tomlString: string- The modified TOML string to update with
overwrite(tomlString)
- Overwrites the internal AST by fully re-parsing the supplied TOML string
- Simpler but slower than
update()which uses incremental parsing - Parameters:
tomlString: string- The TOML string to overwrite with
patch() Example
Using patch() to modify values while preserving formatting
import * as TOML from '@decimalturn/toml-patch';
// or: import { TomlDocument } from '@decimalturn/toml-patch';
const doc = new TOML.TomlDocument(`
# Configuration file
title = "My App"
version = "1.0.0"
[database]
host = "localhost"
port = 5432
`);
// Modify the JavaScript object
const config = doc.toJsObject;
config.version = "2.0.0";
config.database.port = 3306;
config.database.name = "myapp_db";
// Apply changes while preserving comments and formatting
doc.patch(config);
console.log(doc.toTomlString);
// Output:
// # Configuration file
// title = "My App"
// version = "2.0.0"
//
// [database]
// host = "localhost"
// port = 3306
// name = "myapp_db"update() Example
Using update() for efficient incremental parsing when the TOML string was edited
import * as TOML from '@decimalturn/toml-patch';
// or: import { TomlDocument } from '@decimalturn/toml-patch';
const originalToml = `
# Server configuration
[server]
host = "localhost"
port = 8080
debug = true
`;
const doc = new TOML.TomlDocument(originalToml);
// Make a small change to the TOML string
const updatedToml = originalToml.replace('port = 8080', 'port = 3000');
// Efficiently update - only re-parses the changed portion
doc.update(updatedToml);
console.log(doc.toJsObject.server.port); // 3000When to use TomlDocument vs Functional API
| Use Case | TomlDocument | Functional API |
|----------|-------------|----------------|
| Multiple operations on same document | ✅ Preferred | ❌ Inefficient |
| One-time parsing/patching | ⚠️ Overkill | ✅ Preferred |
| Incremental text updates | ✅ update() method | ❌ Not supported |
| Preserving document state | ✅ Built-in | ❌ Manual |
| Working with large files | ✅ Better performance | ❌ Re-parses entirely |
Formatting
The TomlFormat class provides comprehensive control over how TOML documents are formatted during stringification and patching operations. This class encapsulates all formatting preferences, making it easy to maintain consistent styling across your TOML documents.
TomlFormat Class
class TomlFormat {
newLine: string
trailingNewline: number
trailingComma: boolean
bracketSpacing: boolean
inlineTableStart?: number
truncateZeroTimeInDates: boolean
static default(): TomlFormat
static autoDetectFormat(tomlString: string): TomlFormat
}Basic Usage
The recommended approach is to start with TomlFormat.default() and override specific options as needed:
import { patch, stringify, TomlFormat } from '@decimalturn/toml-patch';
// Create a custom format configuration
const format = TomlFormat.default();
format.newLine = '\r\n'; // Windows line endings
format.trailingNewline = 0; // No trailing newline
format.trailingComma = true; // Add trailing commas
format.bracketSpacing = false; // No spaces in brackets
// Use with stringify
const toml = stringify({
title: 'My App',
tags: ['dev', 'config'],
database: { host: 'localhost', port: 5432 }
}, format);
Formatting Options
newLine
- Type:
string - Default:
'\n' - Description: The line ending character(s) to use in the output TOML. This option affects only the stringification process, not the internal representation (AST).
const format = TomlFormat.default();
format.newLine = '\n'; // Unix/Linux line endings
format.newLine = '\r\n'; // Windows line endingstrailingNewline
- Type:
number - Default:
1 - Description: The number of trailing newlines to add at the end of the TOML document. This option affects only the stringification process, not the internal representation (AST).
const format = TomlFormat.default();
format.trailingNewline = 0; // No trailing newline
format.trailingNewline = 1; // One trailing newline (standard)
format.trailingNewline = 2; // Two trailing newlines (adds extra spacing)trailingComma
- Type:
boolean - Default:
false - Description: Whether to add trailing commas after the last element in arrays and inline tables.
const format = TomlFormat.default();
format.trailingComma = false; // [1, 2, 3] and { x = 1, y = 2 }
format.trailingComma = true; // [1, 2, 3,] and { x = 1, y = 2, }bracketSpacing
- Type:
boolean - Default:
true - Description: Whether to add spaces after opening brackets/braces and before closing brackets/braces in arrays and inline tables.
const format = TomlFormat.default();
format.bracketSpacing = true; // [ 1, 2, 3 ] and { x = 1, y = 2 }
format.bracketSpacing = false; // [1, 2, 3] and {x = 1, y = 2}inlineTableStart
- Type:
number(optional) - Default:
1 - Description: The nesting depth at which new tables should start being formatted as inline tables. When adding new tables during patching or stringifying objects, tables at depth bigger or equal to
inlineTableStartwill be formatted as inline tables, while tables at depth smaller thaninlineTableStartwill be formatted as separate table sections. Note that a table at the top-level of the TOML document is considered to have a depth of 0.
const format = TomlFormat.default();
format.inlineTableStart = 0; // All tables are inline tables including top-level
format.inlineTableStart = 1; // Top-level tables as sections, nested tables as inline (default)
format.inlineTableStart = 2; // Two levels as sections, deeper nesting as inlineExample with inlineTableStart = 0:
// With inlineTableStart = 0, all tables become inline
const format = TomlFormat.default();
format.inlineTableStart = 0;
stringify({ database: { host: 'localhost', port: 5432 } }, format);
// Output: database = { host = "localhost", port = 5432 }Example with inlineTableStart = 1 (default):
// With inlineTableStart = 1, top-level tables are sections
const format = TomlFormat.default();
format.inlineTableStart = 1;
stringify({ database: { host: 'localhost', port: 5432 } }, format);
// Output:
// [database]
// host = "localhost"
// port = 5432truncateZeroTimeInDates
- Type:
boolean - Default:
false - Description: When
true, JavaScript Date objects with all time components set to zero (midnight UTC) are automatically serialized as date-only values in TOML. This only affects new values during stringify operations; existing TOML dates maintain their original format during patch operations.
const format = TomlFormat.default();
format.truncateZeroTimeInDates = false; // new Date('2024-01-15T00:00:00.000Z') → 2024-01-15T00:00:00.000Z
format.truncateZeroTimeInDates = true; // new Date('2024-01-15T00:00:00.000Z') → 2024-01-15Example with mixed dates:
import { stringify, TomlFormat } from '@decimalturn/toml-patch';
const format = TomlFormat.default();
format.truncateZeroTimeInDates = true;
const data = {
startDate: new Date('2024-01-15T00:00:00.000Z'), // Will be: 2024-01-15
endDate: new Date('2024-12-31T23:59:59.999Z') // Will be: 2024-12-31T23:59:59.999Z
};
stringify(data, format);
// Output:
// startDate = 2024-01-15
// endDate = 2024-12-31T23:59:59.999ZAuto-Detection and Patching
The TomlFormat.autoDetectFormat() method analyzes existing TOML strings to automatically detect and preserve their current formatting. If you don't supply the format argument when patching an existing document, this is what will be used to determine the formatting to use when inserting new elements.
Note that formatting of existing elements of a TOML string won't be affected by the format passed to patch() except for newLine and trailingNewline which are applied at the document level.
Complete Example
Here's a comprehensive example showing different formatting configurations:
import { stringify, TomlFormat } from '@decimalturn/toml-patch';
const data = {
title: 'Configuration Example',
settings: {
debug: true,
timeout: 30
},
servers: ['web1', 'web2', 'db1'],
database: {
host: 'localhost',
port: 5432,
ssl: true
}
};
// Compact formatting (minimal whitespace)
const compact = TomlFormat.default();
compact.bracketSpacing = false;
compact.trailingNewline = 0;
console.log(stringify(data, compact));
// Output:
// title = "Configuration Example"
// servers = ["web1", "web2", "db1"]
//
// [settings]
// debug = true
// timeout = 30
//
// [database]
// host = "localhost"
// port = 5432
// ssl = true
// Spacious formatting (with trailing commas and extra spacing)
const spacious = TomlFormat.default();
spacious.trailingComma = true;
spacious.bracketSpacing = true;
spacious.trailingNewline = 2;
console.log(stringify(data, spacious));
// Output:
// title = "Configuration Example"
// servers = [ "web1", "web2", "db1", ]
//
// [settings]
// debug = true
// timeout = 30
//
// [database]
// host = "localhost"
// port = 5432
// ssl = true
//
//
// Windows-style formatting
const windows = TomlFormat.default();
windows.newLine = '\r\n';
windows.bracketSpacing = false;
windows.trailingNewline = 1;
console.log(stringify(data, windows));
// Same structure as compact but with \r\n line endingsLegacy Format Objects
For backward compatibility, you can still use anonymous objects for formatting options.
// Legacy approach (still supported)
const result = stringify(data, {
trailingComma: true,
bracketSpacing: false
});
// Recommended approach
const format = TomlFormat.default();
format.trailingComma = true;
format.bracketSpacing = false;
const result = stringify(data, format);Development
- Update submodules:
git submodule update --remote - Typecheck:
npm run typecheck - Build:
npm run build - Test:
npm test - Specs compliance:
npm run specs - Benchmark:
npm run benchmark
[^1]: Tim Hall has been inactive on most of his open source projects for more than 3 years. The sentence wording was inspired by the npm-run-all2 project.
