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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@sigx/lynx-file-system

v0.11.0

Published

File system access for sigx-lynx

Readme

@sigx/lynx-file-system

File read/write/delete plus document and cache directory paths for sigx-lynx. Scoped to the app's sandbox — no broad storage access required.

📚 Documentation

Full guides, API reference and live examples → https://sigx.dev/lynx/modules/file-system/overview/

Install

pnpm add @sigx/lynx-file-system

sigx prebuild auto-discovers and links the native module. No special permissions — both platforms expose per-app document/cache directories without runtime grants.

Usage

import { FileSystem } from '@sigx/lynx-file-system';
const docs = FileSystem.getDocumentDirectory();
await FileSystem.writeFile(`${docs}/data.json`, JSON.stringify({ key: 'value' }));
const content = await FileSystem.readFile(`${docs}/data.json`);
const info = await FileSystem.getInfo(`${docs}/data.json`);
if (info.exists) {
    await FileSystem.deleteFile(`${docs}/data.json`);
}

API

| Method | Notes | | ------------------------------------------------------- | -------------------------------------------------------------------------------------------------- | | getDocumentDirectory(): string | Sync. Persistent app data — survives app updates, included in iCloud/Android backup. | | getCacheDirectory(): string | Sync. Disposable storage — OS may purge under disk pressure. | | writeFile(path: string, content: string): Promise<void> | UTF-8 text. Creates parent directories as needed. | | readFile(path: string): Promise<string> | UTF-8 text. Throws if the file doesn't exist. | | readFileBase64(path: string): Promise<string> | Raw bytes, base64-encoded. Also accepts file:// and (Android) content:// URIs — anything a picker hands back. | | readFileAsArrayBuffer(path: string): Promise<ArrayBuffer> | readFileBase64 decoded to an ArrayBuffer. | | deleteFile(path: string): Promise<void> | No-op if the file doesn't exist. | | getInfo(path: string): Promise<FileInfo> | Always returns a FileInfo — check exists for presence. | | isAvailable(): boolean | Whether the native module is registered in the current build. |

interface FileInfo {
    uri: string;
    size: number;
    exists: boolean;
    isDirectory: boolean;
    modifiedAt: number;     // epoch milliseconds
}

Gotchas

  • Text-only writes. writeFile is UTF-8 text. Reads can be binary via readFileBase64 / readFileAsArrayBuffer, but the whole file is materialized in memory (base64 is ~33% larger crossing the bridge) — fine for small/medium files, wrong for uploads or large media; keep using Camera / ImagePicker / FilePicker URIs directly where possible.
  • Path conventions. Always prefix paths with getDocumentDirectory() or getCacheDirectory(). Raw /data.json won't resolve consistently across platforms.