npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@stenway/sml-io

v1.1.0

Published

Read and write SML files

Downloads

13

Readme

SML-IO

About this package

This package is the Node.js-specific part mentioned in the environment-independent SML package (You will find more information there about SML in general). This package uses Node.js's file system module and offers simple classes to load and save SML files. It offers stream reader and writer classes to read and write SML files node-by-node.

If you want to get a first impression on how to use this package, you can watch this video. But always check the changelog of the presented packages for possible changes, that are not reflected in the video.

Getting started

First get the SML-IO package installed with a package manager of your choice. If you are using NPM just run the following command:

npm install @stenway/sml-io

We are going to use the SML-IO package to write and read some SML files. For that we import the SmlFile class from the SML-IO package. We take this example, parse it as an SmlDocument and save it as a file with the static method saveSync of the SmlFile class.

import { SmlDocument } from "@stenway/sml"
import { SmlFile } from "@stenway/sml-io"

const content = `PointOfInterest
  City      Seattle
  Name      "Space Needle"
  GpsCoords 47.6205 -122.3493
  # Opening hours should go here
End`

const document = SmlDocument.parse(content)
SmlFile.saveSync(document, "Test.sml")

After running the example, the file will be written. It uses the default ReliableTXT encoding UTF-8. If we want to change the used encoding, we can simply set the encoding property of the SmlDocument object. Here we switch to the UTF-16 encoding, and save the document as another file. Note that you need to import the ReliableTxtEncoding enum from the ReliableTXT package.

document.encoding = ReliableTxtEncoding.Utf16
SmlFile.saveSync(document, "TestUtf16.sml")

The file will be written with the UTF-16 encoding.

Now let's load these files again, with the static method loadSync of the SmlFile class. We can see that the encoding of the first file was correctly detected. As well as for the second file.

const loadedDocument = SmlFile.loadSync("Test.sml")
console.log(loadedDocument.encoding)

const loadedDocumentUtf16 = SmlFile.loadSync("TestUtf16.sml")
console.log(loadedDocumentUtf16.encoding)

Errors

When we load a file, there are several things that can go wrong. We'll now have a look at some of the SML-related error types. The first scenario is where the SML file does not have a valid preamble and will throw a ReliableTXT related error. To test that, we can remove the UTF-8 BOM from the file, by saving it as UTF-8 file without the BOM in a text editor that supports this functionality.

When the byte order mark is gone and we load the file, a NoReliableTxtPreambleError will be thrown and the loading of the file will be aborted. Switching back the encoding to UTF-8 with the byte order mark again, the file will loaded without any error.

The next scenario would be to remove one of the enclosing doublequotes from the name value, which would will lead to a WsvParserError.

And finally we can produce an SmlParserError, by removing the end keyword on the last line.

And this way, we can more precisely detected, what was going wrong.

Big SML files

Concerning big SML files, you can watch the ReliableTXT NPM package video that illustrates the problem of string and file size limits of V8 and Node.js, or read the part about big WSV files in the WSV package documentation. This limitation leads to certain restrictions when it comes to writing and reading bigger files in one take. The SML IO package uses the WSV IO package and thus the ReliableTXT IO package so the same limits apply here as well, concerning the saveSync and loadSync method. The limits also might vary between Node.js versions.

With version 20 of Node.js you can say roughly, a 500MB SML file can be written and read in one take, but if you need bigger files you should use the stream writer and reader classes.

Streaming classes

We'll now have a look the synchronous SmlStreamWriter class. We first need an SmlDocument object as template, which contains information about the name of the root element, or indentation settings, or the end keyword. We then create a SyncSmlStreamWriter object by passing the template document and the file path as arguments.

import { SmlDocument, SmlElement } from "@stenway/sml"
import { SyncSmlStreamWriter } from "@stenway/sml-io"

const template = new SmlDocument(new SmlElement("POIs"))
const writer = SyncSmlStreamWriter.create(template, "Stream.sml")
try {
	for (let i=0; i<100; i++) {
		const element = new SmlElement("POI")
		element.addAttribute("Name", [`Point of Interest ${i+1}`])
		element.addAttribute("GpsCoords", [`${i+1}`, i.toString()])
		writer.writeNode(element)
	}
} finally {
	writer.close()
}

We iterate a hundred times and write an element with two attributes, which we will vary by using the iterator variable to create different values. We use the writeNode method of the writer class to write the element to the stream. After the iteration we close the stream writer.

In order to append SML nodes to an existing SML file, we can create a stream writer in append mode. Here we first append an empty line with a comment and then append 10 attributes.

const appendingWriter = SyncSmlStreamWriter.create(template, "Stream.sml", WriterMode.CreateOrAppend)
try {
	appendingWriter.writeNode(new SmlEmptyNode(null, " And now some attributes"))
	for (let i=0; i<10; i++) {
		appendingWriter.writeNode(
			new SmlAttribute("POI", [`Point of Interest ${i+1}`, `${i+1}`, i.toString()])
		)
	}
} finally {
	appendingWriter.close()
}

Note that the WriterMode enum needs to be imported from the ReliableTXT package.

And now we want to test the synchronous SmlStreamReader. For that we create a new reader object by passing the file path to the constructor. To test, if we are loading an SML file with the correct format, we do a preliminary check of the root element's name with the assureName method.

const reader = SyncSmlStreamReader.create("Stream.sml")
try {
	reader.root.assureName("POIs")
	let numElements = 0
	let numAttributes = 0
	let numEmptyNodes = 0
	while (true) {
		const node = reader.readNode()
		if (node === null) { break }
		if (node.isElement()) { numElements++ }
		else if (node.isAttribute()) { numAttributes++ }
		else { numEmptyNodes++ }
	}
	console.log(`Elements: ${numElements} Attributes: ${numAttributes} Empty: ${numEmptyNodes}`)
} finally {
	reader.close()
}

We then loop over the file and retrieve the next node with the readNode method. When the file end was reached, the method will return null and we can exit our loop. The read node can be an element, an attribute or an empty line. In this example we will simply count these three types, and should get values that match what we were writing before.

And if we run the example, we will see, it counted correctly 100 elements, 10 attributes, and one single comment line.

Asynchronous IO

All methods and classes come as synchronous and asynchronous versions. The saveSync and loadSync methods for example are synchronous, and the save and load methods of the SmlFile class are asynchronous:

const document = SmlDocument.parse("Root\nEnd")
await SmlFile.save(document, "Test.sml")
const loadedDocument = await SmlFile.load("Test.sml")

An asynchronous stream reader for example can be created analogously to the synchronous variant:

const reader = await SmlStreamReader.create("Stream.sml")

BinarySML Files

BinarySML is the binary representation of SML documents. It starts with the magic code 'BS1'. BinarySML is made for scenarios, where parsing speed of the textual representation might be a limitation. You can learn more about it in the SML package documentation.

To save and load BinarySML files simply use the BinarySmlFile class.

const document = SmlDocument.parse("Root\nEnd")
BinarySmlFile.saveSync(document, "Test.bsml")
const loadedDocument = BinarySmlFile.loadSync("Test.bsml")

SML files are suited to append content to them. BinarySML files however have an advantage when appending nodes, because in contrary to the textual version, the end part does not need to be truncated and thus content can directly be appended.

To read and write BinarySML files in a node-by-node fashion, simply use the SyncBinaryWsvStreamReader, BinaryWsvStreamReader, SyncBinaryWsvStreamWriter, and BinaryWsvStreamWriter classes, which work analogously to their textual version counterparts.