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

@xan105/ini

v2.2.0

Published

An opinionated ini encoder/decoder with comment-preserving feature.

Downloads

35

Readme

About

An opinionated ini encoder/decoder with comment-preserving feature.

Originally created due to several issues when using npm/ini and alternatives.

📦 Scoped @xan105 packages are for my own personal use but feel free to use them.

Example

import { parse, stringify } from "@xan105/ini";
import { readFile, writeFile } from "node:fs/promises";

const file = await readFile("path/to/ini", "utf8");
const data = parse(file);
//do something
await writeFile("path/to/ini", data, "utf8");

Install

npm install @xan105/ini

API

⚠️ This module is only available as an ECMAScript module (ESM) starting with version 2.0.0. Previous version(s) are CommonJS (CJS) with an ESM wrapper.

Named export

parse(string: string, option?: object): object

Decode the ini-style formatted string into an object.

⚙️ Options

  • translate:? boolean | object

    Auto string convertion.

    💡 Translate option accepts an object for granular control or a boolean which will force all following options to true/false:

    • bool?: boolean (true) String to boolean.

    • number?: boolean (false) String to number or bigint.

    • unsafe?: boolean (false) Set to true to keep unsafe integer instead of bigint.

    • unquote?: boolean (false) Remove leading and trailing quotes (" or ').

  • ignoreGlobalSection?: boolean (false) Ignore keys without a section aka 'Global' section.

  • sectionFilter?: string[] List of section name to filter out.

  • comment?: boolean (true) When set to true comments are stored in the symbol property comment of the returned object otherwise they are ignored.

  • removeInline?: boolean (false) Remove illegal inline comment. ⚠️ Can have false positive. Use with caution.

📝 Implementation notice

  • Sections cannot be nested.
  • Comments start with ; or #.
  • Inline comments are not allowed !
    • Section: they are ignored.
    • Value: they are considered as part of the value unless you use the removeInline option to strip them.
  • Duplicate keys: override first occurrence.
  • Case sensitive.
  • Key/value delimiter is = and is mandatory.
  • Whitespaces around section, key and value are trimmed.
  • One key/value per line

⚠️ JSON compatibility

Some integers will be represented as BigInt due to their size if the related translate options are used. BigInt is not a valid value in the JSON spec. As such when stringify-ing the returned object to JSON you'll need to handle the JSON stringify replacer function to prevent it to fail.

A common workaround is to represent them as a string:

JSON.stringify(data, function(key, value) {
  if(typeof value === "bigint")
    return value.toString();
  else
    return value;
});

stringify(obj: object, option?: object): string

Encode the object obj into an ini-style formatted string.

⚙️ Options

  • whitespace?: boolean (false) Whether to put whitespace around the delimiter =.

  • blankLine?: boolean (true) Add blank lines between sections.

  • ignoreGlobalSection?: boolean (false) Ignore root properties (not under any namespace if you will).

  • quoteString?: boolean (false) Quote string values using double quotes ("...").

  • comment?: boolean (true) Restore comments from the symbol property comment of the given object (if any).

  • eol?: string (system's EOL) Either "\n" (POSIX) or "\r\n" (Windows).

📝 Implementation notice

  • Sections shall not be nested.
  • Case sensitive.
  • Empty sections are allowed.
  • Value can only be a boolean, number, bigint or string.