{
"repo": "bare-node",
"timestamp": "2026-01-16T23:55:44.082Z",
"entryPoint": "index.js",
"exports": {
"packageJson": {}
},
"api": {},
"readme": {
"content": "# bare-node\n\nCompatibility modules for Bare that try to behave like their Node.js counterparts. Not meant to cover 100% of all APIs but the 95% that everyone uses.\n\n## Usage\n\nTo use any of the supported Node.js builtins, such as `fs`, in a Bare application run the following:\n\n```\nnpm i bare-fs fs@npm:bare-node-fs\n```\n\nThis will add something like the following to your `package.json`:\n\n```json\n{\n \"dependencies\": {\n \"bare-fs\": \"^2.1.5\",\n \"fs\": \"npm:bare-node-fs\"\n }\n}\n```\n\nThe only thing the wrapper does is `module.exports = require('bare-fs')` and at version `*`, meaning the version you specify is the one that wins. Using the wrapper saves you space as it means npm will only include `bare-fs` once even if multiple modules depend on it.\n\n### Import maps\n\nWhen writing a module that uses a Node.js builtin, such as `fs`, you can also choose to specify directly in that module what builtin should map to instead of relying on the compatibility layer. You would do that using an import ma",
"sections": [
"intro",
"usage",
"modules",
"license"
],
"hasApi": true,
"hasExamples": true,
"exampleCount": 2,
"examples": [
"npm i bare-fs fs@npm:bare-node-fs",
"The only thing the wrapper does is `module.exports = require('bare-fs')` and at version `*`, meaning the version you specify is the one that wins. Using the wrapper saves you space as it means npm will only include `bare-fs` once even if multiple modules depend on it.\n\n### Import maps\n\nWhen writing a module that uses a Node.js builtin, such as `fs`, you can also choose to specify directly in that module what builtin should map to instead of relying on the compatibility layer. You would do that using an import map by adding the following to your `package.json`:"
]
},
"patterns": []
}