https://github.com/privatenumber/fs-require
Create a require() function from any file-system. Great for in-memory fs testing!
https://github.com/privatenumber/fs-require
fs fs-require memfs require testing
Last synced: about 1 year ago
JSON representation
Create a require() function from any file-system. Great for in-memory fs testing!
- Host: GitHub
- URL: https://github.com/privatenumber/fs-require
- Owner: privatenumber
- Created: 2021-05-23T21:09:31.000Z (almost 5 years ago)
- Default Branch: develop
- Last Pushed: 2022-12-05T14:36:38.000Z (over 3 years ago)
- Last Synced: 2025-03-17T12:06:34.717Z (about 1 year ago)
- Topics: fs, fs-require, memfs, require, testing
- Language: TypeScript
- Homepage:
- Size: 339 KB
- Stars: 16
- Watchers: 2
- Forks: 1
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# fs-require [](https://npm.im/fs-require) [](https://npm.im/fs-require) [](https://packagephobia.now.sh/result?p=fs-require) [](https://bundlephobia.com/result?p=fs-require)
Create a `require()` function from any file-system.
Pass in a [virtual file-system](https://github.com/streamich/memfs) for in-memory testing without writing to disk.
### Features
- 💞 Works well with [memfs](https://github.com/streamich/memfs)!
- 🪄 Resolves implicit entry `index` and implicit extensions `js` and `json`
- 🗺 Resolves relative and absolute paths
- 📍 `__dirname` & `__filename`
- ✅ `require.resolve()` & `require.cache`
- 👻 Mocks `fs` within fsRequire
- 👣 Call stack shows paths with `fs-require://` protocol
Support this project by ⭐️ starring and sharing it. [Follow me](https://github.com/privatenumber) to see what other cool projects I'm working on! ❤️
## 🚀 Install
```bash
npm i fs-require
```
## 🙋♀️ Why?
Using fs-require with [memfs](https://github.com/streamich/memfs) is a great combination for writing tests that interact with the file-system.
Testing functionality that interacts with the file-system can be brittle because they expect a clean slate and can also be dangerous if the path is wrong. Creating a virtual file-system with `memfs` and testing its contents with `fsRequire` makes it secure and fast!
## 👨🏫 Usage
```js
import { Volume } from 'memfs'
import { createFsRequire } from 'fs-require'
// Create a virtual fs from JSON
const virtualFs = Volume.fromJSON({
'/hello-world.js': `
module.exports = function () {
return 'Hello world!'
}
`
})
// Create fsRequire
const fsRequire = createFsRequire(virtualFs)
// Import virtual module
const helloWorld = fsRequire('/hello-world')
console.log(helloWorld()) // Hello world!
```
## ⚙️ API
### createFsRequire(fs, options?)
Returns a `fsRequire(modulePath)` function that resolves from the file-system passed in.
#### fs
Type: `FileSystem`
Required
The file-system to resolve requires from.
#### options
##### options.fs
Type: `boolean | FileSystem`
Code executed the virtual file-system may `require('fs')` and this may either pose as a security concern or yield inconsistent results as the virtual file won't not accessible through the actual `fs` module.
By default `require('fs')` is shimmed to the file-system passed into `createFsRequire`.
To disable this behavior and resolve to the real `fs` module, set this to `true`.
You can also pass in a different file-system too.
### fsRequire(modulePath)
#### modulePath
Type: `string`
Required
Path to the module you want to "require". Mocks Node.js [`require`](https://nodejs.org/api/modules.html#requireid).
### fsRequire.resolve(modulePath)
#### modulePath
Type: `string`
Required
Path to the module you want to "resolve". Mocks Node.js [`require.resolve`](https://nodejs.org/api/modules.html#requireresolverequest-options).
### fsRequire.cache
Type: `Record`
An object that contains the cache for modules that have been loaded so far. The key is the absolute path to the module, and the value is the module instance. Mocks Node.js [`require.cache`](https://nodejs.org/api/modules.html#requirecache).
To re-load a module that has already been loaded, you can delete the cache the same way you would in Node.js:
```js
delete fsRequire.cache[fsRequire.resolve('/some-module.js')]
```
## 💁♂️ FAQ
### Can it resolve case insensitive paths?
Case sensitivity in paths is a file-system concern so it would depend on the `fs` passed in. For example, [macOS (native fs) is case insensitive](https://discussions.apple.com/thread/251191099#:~:text=No.,have%20two%20files%20named%20File.). [memfs is case sensitive](https://github.com/streamich/memfs/issues/533).
## 👨👩👧 Related
- [fs-monkey](https://github.com/streamich/fs-monkey) - By the same author of [memfs](https://github.com/streamich/memfs). Patches the global `require` to access a virtual fs.