This repository was archived by the owner on Aug 5, 2020. It is now read-only.

Repository files navigation

Node.js: fs-filesystem

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

npm versionTravis Build StatusWindows Build StatusCoverage StatusDependencies Status

Why?

Because sometimes your desktop applications need information about the filesystem (*cough* like on Windows *cough*)

Installation

npm install --save fs-filesystem

Native Dependencies

Bear in mind that this utility shells out to the machine, and thus requires the host to be able to run such commands. If any of the commands listed below are missing from your OS, the utility will throw a Command Failed: ... error. This shouldn't be a problem however since these are standard, core commands generally available on their respective distros (well, except maybe minimal Linux distros like Arch and Alpine), so you should be fine :)

  • Linux:df, fdisk, lsblk
  • MacOS:diskutil
  • Windows:wmic

API

Async

importfilesystemfrom'fs-filesystem';filesystem(filter,(err,result)=>{console.log('devices',result);});

filesystem( [ filter , ], callback )

// filesystem :: string|RegExp|function|undefined|null, function -> void

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices
  • callback {function}: Function following the common Node.js callback style, i.e. taking a (err, value) => ...

If only a function is provided to filesystem, the utility will assume that it is the callback function.

Wanna get rid of the callback? Try util.promisify for Node >=8, bluebird's Promise.promisify or universalify ;)

Sync

import{filesystemSync}from'fs-filesystem';constresult=filesystemSync(filter);console.log('devices',result);

filesystemSync( [ filter ] )

Remember, it's usually discouraged to use sync functions except when doing early setup!

// filesystemSync :: string|RegExp|function|undefined|null -> Object

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices

What Data Can I Expect?

fs-filesystem will return a hash object of all the devices available on the computer, whether networked, internal or external/removable. Their respective volumes are available as an array of volumes under the device.volumes property. Linux and MacOS users will be pleased with the amount of detail available - block size, partition type, filesystem, mounted, mount point, blocks, and more is available. Windows users fall on the short straw however with a much less rich output. This is because (a) the main maintainer of fs-filesystem has very little knowledge of DOS/PowerShell utilities and (b) there seems to be very little filesystem utilities available on Windows that do not require elevated privileges. So if you are a Windows DemiGod, feel free to enlighten us 🚀

Sample Outputs

MacOS

{
"disk1": {
"id": "disk1",
"node": "/dev/disk1",
"whole": true,
"parent": "disk1",
"name": null,
"size": 2000398934016,
"description": "APPLE HDD ST2000DM001",
"protocol": "SATA",
"blockSize": 512,
"removable": true,
"mounted": false,
"volumes": [
{
"id": "disk1s1",
"node": "/dev/disk1s1",
"whole": false,
"parent": "disk1",
"name": "EFI",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "EFI",
"fs": "FAT32",
"space": {
"total": 0,
"available": 0,
"used": 0
}
},
{
"id": "disk1s2",
"node": "/dev/disk1s2",
"whole": false,
"parent": "disk1",
"name": "Recovery HD",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "Apple_Boot",
"fs": "HFS+",
"space": {
"total": 0,
"available": 0,
"used": 0
}
}
]
}
}

Linux

{
"sda": {
"id": "sda",
"node": "/dev/sda",
"whole": true,
"parent": "sda",
"name": "sda",
"size": 250059350016,
"description": null,
"protocol": null,
"blockSize": 512,
"readOnly": false,
"removable": false,
"blocks": 488397168,
"volumes": [
{
"id": "sda2",
"node": "/dev/sda2",
"whole": false,
"parent": "sda",
"name": "sda2",
"description": "Linux filesystem",
"blockSize": 512,
"blocks": 455499776,
"readOnly": false,
"mounted": true,
"mountPoint": "/",
"partitionType": null,
"fs": "ext4",
"space": {
"total": 229421658112,
"available": 21887852544,
"used": 195856236544
},
"removable": false
},
{
"id": "sda1",
"node": "/dev/sda1",
"whole": false,
"parent": "sda",
"name": "sda1",
"description": "BIOS boot",
"blockSize": 512,
"blocks": 2048,
"readOnly": false,
"mounted": false,
"mountPoint": null,
"partitionType": null,
"fs": null,
"space": {
"total": null,
"available": null,
"used": null
},
"removable": false
}
]
}
}

Windows

{
"C:": {
"id": "C:",
"node": "C:",
"whole": true,
"parent": "C:",
"name": "C:",
"size": 22288527360,
"description": "Local Fixed Disk",
"protocol": null,
"blockSize": null,
"readOnly": null,
"removable": null,
"volumes": [
{
"id": "C:",
"node": "C:",
"whole": false,
"parent": "C:",
"name": null,
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": "C:",
"partitionType": null,
"fs": "NTFS",
"space": {
"total": 22288527360,
"available": 4928057344,
"used": 17360470016
}
}
]
}
}

Data Types

You can find a list of the types of each field below. Keep in mind that all fields besides whole are null by default, and that integers are all in bytes.

Devices

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
size: integer,
description: string,
protocol: string,
blockSize: integer,
readOnly: boolean,
removable: boolean

Volumes

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
description: string,
blockSize: number,
blocks: number,
readOnly: boolean,
mounted: boolean,
mountPoint: boolean,
partitionType: string,
fs: string,
space: {
total: number,
available: number,
used: number
}

About

NodeJS Filesystem Utility

Resources

Stars

21 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Add copy buttons to all
 blocks\n(function() {\n function addCopyButtons() {\n document.querySelectorAll('pre code').forEach(function(codeBlock) {\n if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;\n codeBlock.parentElement.setAttribute('data-copy-added', 'true');\n \n var btn = document.createElement('button');\n btn.textContent = 'Copy';\n btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';\n btn.onmouseover = function() { this.style.opacity = '1'; };\n btn.onmouseout = function() { this.style.opacity = '0.7'; };\n btn.onclick = function() {\n navigator.clipboard.writeText(codeBlock.textContent).then(function() {\n btn.textContent = 'Copied!';\n setTimeout(function() { btn.textContent = 'Copy'; }, 1500);\n });\n };\n codeBlock.parentElement.style.position = 'relative';\n codeBlock.parentElement.appendChild(btn);\n });\n }\n \n addCopyButtons();\n \n // Re-run on dynamic content\n var observer = new MutationObserver(addCopyButtons);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Add Copy Buttons to Code Blocks");
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
Skip to content
This repository was archived by the owner on Aug 5, 2020. It is now read-only.

Repository files navigation

Node.js: fs-filesystem

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

npm versionTravis Build StatusWindows Build StatusCoverage StatusDependencies Status

Why?

Because sometimes your desktop applications need information about the filesystem (*cough* like on Windows *cough*)

Installation

npm install --save fs-filesystem

Native Dependencies

Bear in mind that this utility shells out to the machine, and thus requires the host to be able to run such commands. If any of the commands listed below are missing from your OS, the utility will throw a Command Failed: ... error. This shouldn't be a problem however since these are standard, core commands generally available on their respective distros (well, except maybe minimal Linux distros like Arch and Alpine), so you should be fine :)

  • Linux:df, fdisk, lsblk
  • MacOS:diskutil
  • Windows:wmic

API

Async

importfilesystemfrom'fs-filesystem';filesystem(filter,(err,result)=>{console.log('devices',result);});

filesystem( [ filter , ], callback )

// filesystem :: string|RegExp|function|undefined|null, function -> void

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices
  • callback {function}: Function following the common Node.js callback style, i.e. taking a (err, value) => ...

If only a function is provided to filesystem, the utility will assume that it is the callback function.

Wanna get rid of the callback? Try util.promisify for Node >=8, bluebird's Promise.promisify or universalify ;)

Sync

import{filesystemSync}from'fs-filesystem';constresult=filesystemSync(filter);console.log('devices',result);

filesystemSync( [ filter ] )

Remember, it's usually discouraged to use sync functions except when doing early setup!

// filesystemSync :: string|RegExp|function|undefined|null -> Object

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices

What Data Can I Expect?

fs-filesystem will return a hash object of all the devices available on the computer, whether networked, internal or external/removable. Their respective volumes are available as an array of volumes under the device.volumes property. Linux and MacOS users will be pleased with the amount of detail available - block size, partition type, filesystem, mounted, mount point, blocks, and more is available. Windows users fall on the short straw however with a much less rich output. This is because (a) the main maintainer of fs-filesystem has very little knowledge of DOS/PowerShell utilities and (b) there seems to be very little filesystem utilities available on Windows that do not require elevated privileges. So if you are a Windows DemiGod, feel free to enlighten us 🚀

Sample Outputs

MacOS

{
"disk1": {
"id": "disk1",
"node": "/dev/disk1",
"whole": true,
"parent": "disk1",
"name": null,
"size": 2000398934016,
"description": "APPLE HDD ST2000DM001",
"protocol": "SATA",
"blockSize": 512,
"removable": true,
"mounted": false,
"volumes": [
{
"id": "disk1s1",
"node": "/dev/disk1s1",
"whole": false,
"parent": "disk1",
"name": "EFI",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "EFI",
"fs": "FAT32",
"space": {
"total": 0,
"available": 0,
"used": 0
}
},
{
"id": "disk1s2",
"node": "/dev/disk1s2",
"whole": false,
"parent": "disk1",
"name": "Recovery HD",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "Apple_Boot",
"fs": "HFS+",
"space": {
"total": 0,
"available": 0,
"used": 0
}
}
]
}
}

Linux

{
"sda": {
"id": "sda",
"node": "/dev/sda",
"whole": true,
"parent": "sda",
"name": "sda",
"size": 250059350016,
"description": null,
"protocol": null,
"blockSize": 512,
"readOnly": false,
"removable": false,
"blocks": 488397168,
"volumes": [
{
"id": "sda2",
"node": "/dev/sda2",
"whole": false,
"parent": "sda",
"name": "sda2",
"description": "Linux filesystem",
"blockSize": 512,
"blocks": 455499776,
"readOnly": false,
"mounted": true,
"mountPoint": "/",
"partitionType": null,
"fs": "ext4",
"space": {
"total": 229421658112,
"available": 21887852544,
"used": 195856236544
},
"removable": false
},
{
"id": "sda1",
"node": "/dev/sda1",
"whole": false,
"parent": "sda",
"name": "sda1",
"description": "BIOS boot",
"blockSize": 512,
"blocks": 2048,
"readOnly": false,
"mounted": false,
"mountPoint": null,
"partitionType": null,
"fs": null,
"space": {
"total": null,
"available": null,
"used": null
},
"removable": false
}
]
}
}

Windows

{
"C:": {
"id": "C:",
"node": "C:",
"whole": true,
"parent": "C:",
"name": "C:",
"size": 22288527360,
"description": "Local Fixed Disk",
"protocol": null,
"blockSize": null,
"readOnly": null,
"removable": null,
"volumes": [
{
"id": "C:",
"node": "C:",
"whole": false,
"parent": "C:",
"name": null,
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": "C:",
"partitionType": null,
"fs": "NTFS",
"space": {
"total": 22288527360,
"available": 4928057344,
"used": 17360470016
}
}
]
}
}

Data Types

You can find a list of the types of each field below. Keep in mind that all fields besides whole are null by default, and that integers are all in bytes.

Devices

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
size: integer,
description: string,
protocol: string,
blockSize: integer,
readOnly: boolean,
removable: boolean

Volumes

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
description: string,
blockSize: number,
blocks: number,
readOnly: boolean,
mounted: boolean,
mountPoint: boolean,
partitionType: string,
fs: string,
space: {
total: number,
available: number,
used: number
}

About

NodeJS Filesystem Utility

Resources

Stars

21 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Force GitHub README to respect dark mode\n(function() {\n var style = document.createElement('style');\n style.textContent = '\n .markdown-body {\n color-scheme: dark light;\n }\n .markdown-body pre { background: #161b22 !important; }\n .markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }\n .markdown-body table th, .markdown-body table td { border-color: #30363d !important; }\n .markdown-body img { background: #0d1117; }\n .markdown-body blockquote { border-left-color: #8b949e; }\n .markdown-body hr { border-color: #30363d; }\n ';\n document.head.appendChild(style);\n})();", "GitHub Dark Mode README Fix"); } } catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content
This repository was archived by the owner on Aug 5, 2020. It is now read-only.

Repository files navigation

Node.js: fs-filesystem

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

npm versionTravis Build StatusWindows Build StatusCoverage StatusDependencies Status

Why?

Because sometimes your desktop applications need information about the filesystem (*cough* like on Windows *cough*)

Installation

npm install --save fs-filesystem

Native Dependencies

Bear in mind that this utility shells out to the machine, and thus requires the host to be able to run such commands. If any of the commands listed below are missing from your OS, the utility will throw a Command Failed: ... error. This shouldn't be a problem however since these are standard, core commands generally available on their respective distros (well, except maybe minimal Linux distros like Arch and Alpine), so you should be fine :)

  • Linux:df, fdisk, lsblk
  • MacOS:diskutil
  • Windows:wmic

API

Async

importfilesystemfrom'fs-filesystem';filesystem(filter,(err,result)=>{console.log('devices',result);});

filesystem( [ filter , ], callback )

// filesystem :: string|RegExp|function|undefined|null, function -> void

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices
  • callback {function}: Function following the common Node.js callback style, i.e. taking a (err, value) => ...

If only a function is provided to filesystem, the utility will assume that it is the callback function.

Wanna get rid of the callback? Try util.promisify for Node >=8, bluebird's Promise.promisify or universalify ;)

Sync

import{filesystemSync}from'fs-filesystem';constresult=filesystemSync(filter);console.log('devices',result);

filesystemSync( [ filter ] )

Remember, it's usually discouraged to use sync functions except when doing early setup!

// filesystemSync :: string|RegExp|function|undefined|null -> Object

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices

What Data Can I Expect?

fs-filesystem will return a hash object of all the devices available on the computer, whether networked, internal or external/removable. Their respective volumes are available as an array of volumes under the device.volumes property. Linux and MacOS users will be pleased with the amount of detail available - block size, partition type, filesystem, mounted, mount point, blocks, and more is available. Windows users fall on the short straw however with a much less rich output. This is because (a) the main maintainer of fs-filesystem has very little knowledge of DOS/PowerShell utilities and (b) there seems to be very little filesystem utilities available on Windows that do not require elevated privileges. So if you are a Windows DemiGod, feel free to enlighten us 🚀

Sample Outputs

MacOS

{
"disk1": {
"id": "disk1",
"node": "/dev/disk1",
"whole": true,
"parent": "disk1",
"name": null,
"size": 2000398934016,
"description": "APPLE HDD ST2000DM001",
"protocol": "SATA",
"blockSize": 512,
"removable": true,
"mounted": false,
"volumes": [
{
"id": "disk1s1",
"node": "/dev/disk1s1",
"whole": false,
"parent": "disk1",
"name": "EFI",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "EFI",
"fs": "FAT32",
"space": {
"total": 0,
"available": 0,
"used": 0
}
},
{
"id": "disk1s2",
"node": "/dev/disk1s2",
"whole": false,
"parent": "disk1",
"name": "Recovery HD",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "Apple_Boot",
"fs": "HFS+",
"space": {
"total": 0,
"available": 0,
"used": 0
}
}
]
}
}

Linux

{
"sda": {
"id": "sda",
"node": "/dev/sda",
"whole": true,
"parent": "sda",
"name": "sda",
"size": 250059350016,
"description": null,
"protocol": null,
"blockSize": 512,
"readOnly": false,
"removable": false,
"blocks": 488397168,
"volumes": [
{
"id": "sda2",
"node": "/dev/sda2",
"whole": false,
"parent": "sda",
"name": "sda2",
"description": "Linux filesystem",
"blockSize": 512,
"blocks": 455499776,
"readOnly": false,
"mounted": true,
"mountPoint": "/",
"partitionType": null,
"fs": "ext4",
"space": {
"total": 229421658112,
"available": 21887852544,
"used": 195856236544
},
"removable": false
},
{
"id": "sda1",
"node": "/dev/sda1",
"whole": false,
"parent": "sda",
"name": "sda1",
"description": "BIOS boot",
"blockSize": 512,
"blocks": 2048,
"readOnly": false,
"mounted": false,
"mountPoint": null,
"partitionType": null,
"fs": null,
"space": {
"total": null,
"available": null,
"used": null
},
"removable": false
}
]
}
}

Windows

{
"C:": {
"id": "C:",
"node": "C:",
"whole": true,
"parent": "C:",
"name": "C:",
"size": 22288527360,
"description": "Local Fixed Disk",
"protocol": null,
"blockSize": null,
"readOnly": null,
"removable": null,
"volumes": [
{
"id": "C:",
"node": "C:",
"whole": false,
"parent": "C:",
"name": null,
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": "C:",
"partitionType": null,
"fs": "NTFS",
"space": {
"total": 22288527360,
"available": 4928057344,
"used": 17360470016
}
}
]
}
}

Data Types

You can find a list of the types of each field below. Keep in mind that all fields besides whole are null by default, and that integers are all in bytes.

Devices

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
size: integer,
description: string,
protocol: string,
blockSize: integer,
readOnly: boolean,
removable: boolean

Volumes

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
description: string,
blockSize: number,
blocks: number,
readOnly: boolean,
mounted: boolean,
mountPoint: boolean,
partitionType: string,
fs: string,
space: {
total: number,
available: number,
used: number
}

About

NodeJS Filesystem Utility

Resources

Stars

21 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Highlight search terms from Google/DuckDuckGo/Bing referrer\n(function() {\n var ref = document.referrer;\n var terms = [];\n \n if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {\n var url = new URL(ref);\n var q = url.searchParams.get('q') || url.searchParams.get('p');\n if (q) {\n terms = q.split(/\\s+/).filter(function(t) { return t.length > 2; });\n }\n }\n \n if (terms.length === 0) return;\n \n var style = document.createElement('style');\n style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';\n document.head.appendChild(style);\n \n function highlight(node) {\n if (node.nodeType === 3) { // text node\n var text = node.textContent;\n var found = false;\n terms.forEach(function(term) {\n var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\\]\\\\]/g, '\\\\') + ')', 'gi');\n if (regex.test(text)) {\n found = true;\n var frag = document.createDocumentFragment();\n var parts = text.split(regex);\n parts.forEach(function(part, i) {\n if (i % 2 === 0) {\n frag.appendChild(document.createTextNode(part));\n } else {\n var span = document.createElement('span');\n span.className = 'userscript-highlight';\n span.textContent = part;\n frag.appendChild(span);\n }\n });\n node.parentNode.replaceChild(frag, node);\n }\n });\n } else if (node.nodeType === 1 && node.childNodes) { // element\n var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];\n if (!skipTags.includes(node.tagName)) {\n Array.from(node.childNodes).forEach(highlight);\n }\n }\n }\n \n highlight(document.body);\n \n // Re-highlight on dynamic content\n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1 || node.nodeType === 3) highlight(node);\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Highlight Search Terms"); } } catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content
This repository was archived by the owner on Aug 5, 2020. It is now read-only.

Repository files navigation

Node.js: fs-filesystem

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

npm versionTravis Build StatusWindows Build StatusCoverage StatusDependencies Status

Why?

Because sometimes your desktop applications need information about the filesystem (*cough* like on Windows *cough*)

Installation

npm install --save fs-filesystem

Native Dependencies

Bear in mind that this utility shells out to the machine, and thus requires the host to be able to run such commands. If any of the commands listed below are missing from your OS, the utility will throw a Command Failed: ... error. This shouldn't be a problem however since these are standard, core commands generally available on their respective distros (well, except maybe minimal Linux distros like Arch and Alpine), so you should be fine :)

  • Linux:df, fdisk, lsblk
  • MacOS:diskutil
  • Windows:wmic

API

Async

importfilesystemfrom'fs-filesystem';filesystem(filter,(err,result)=>{console.log('devices',result);});

filesystem( [ filter , ], callback )

// filesystem :: string|RegExp|function|undefined|null, function -> void

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices
  • callback {function}: Function following the common Node.js callback style, i.e. taking a (err, value) => ...

If only a function is provided to filesystem, the utility will assume that it is the callback function.

Wanna get rid of the callback? Try util.promisify for Node >=8, bluebird's Promise.promisify or universalify ;)

Sync

import{filesystemSync}from'fs-filesystem';constresult=filesystemSync(filter);console.log('devices',result);

filesystemSync( [ filter ] )

Remember, it's usually discouraged to use sync functions except when doing early setup!

// filesystemSync :: string|RegExp|function|undefined|null -> Object

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices

What Data Can I Expect?

fs-filesystem will return a hash object of all the devices available on the computer, whether networked, internal or external/removable. Their respective volumes are available as an array of volumes under the device.volumes property. Linux and MacOS users will be pleased with the amount of detail available - block size, partition type, filesystem, mounted, mount point, blocks, and more is available. Windows users fall on the short straw however with a much less rich output. This is because (a) the main maintainer of fs-filesystem has very little knowledge of DOS/PowerShell utilities and (b) there seems to be very little filesystem utilities available on Windows that do not require elevated privileges. So if you are a Windows DemiGod, feel free to enlighten us 🚀

Sample Outputs

MacOS

{
"disk1": {
"id": "disk1",
"node": "/dev/disk1",
"whole": true,
"parent": "disk1",
"name": null,
"size": 2000398934016,
"description": "APPLE HDD ST2000DM001",
"protocol": "SATA",
"blockSize": 512,
"removable": true,
"mounted": false,
"volumes": [
{
"id": "disk1s1",
"node": "/dev/disk1s1",
"whole": false,
"parent": "disk1",
"name": "EFI",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "EFI",
"fs": "FAT32",
"space": {
"total": 0,
"available": 0,
"used": 0
}
},
{
"id": "disk1s2",
"node": "/dev/disk1s2",
"whole": false,
"parent": "disk1",
"name": "Recovery HD",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "Apple_Boot",
"fs": "HFS+",
"space": {
"total": 0,
"available": 0,
"used": 0
}
}
]
}
}

Linux

{
"sda": {
"id": "sda",
"node": "/dev/sda",
"whole": true,
"parent": "sda",
"name": "sda",
"size": 250059350016,
"description": null,
"protocol": null,
"blockSize": 512,
"readOnly": false,
"removable": false,
"blocks": 488397168,
"volumes": [
{
"id": "sda2",
"node": "/dev/sda2",
"whole": false,
"parent": "sda",
"name": "sda2",
"description": "Linux filesystem",
"blockSize": 512,
"blocks": 455499776,
"readOnly": false,
"mounted": true,
"mountPoint": "/",
"partitionType": null,
"fs": "ext4",
"space": {
"total": 229421658112,
"available": 21887852544,
"used": 195856236544
},
"removable": false
},
{
"id": "sda1",
"node": "/dev/sda1",
"whole": false,
"parent": "sda",
"name": "sda1",
"description": "BIOS boot",
"blockSize": 512,
"blocks": 2048,
"readOnly": false,
"mounted": false,
"mountPoint": null,
"partitionType": null,
"fs": null,
"space": {
"total": null,
"available": null,
"used": null
},
"removable": false
}
]
}
}

Windows

{
"C:": {
"id": "C:",
"node": "C:",
"whole": true,
"parent": "C:",
"name": "C:",
"size": 22288527360,
"description": "Local Fixed Disk",
"protocol": null,
"blockSize": null,
"readOnly": null,
"removable": null,
"volumes": [
{
"id": "C:",
"node": "C:",
"whole": false,
"parent": "C:",
"name": null,
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": "C:",
"partitionType": null,
"fs": "NTFS",
"space": {
"total": 22288527360,
"available": 4928057344,
"used": 17360470016
}
}
]
}
}

Data Types

You can find a list of the types of each field below. Keep in mind that all fields besides whole are null by default, and that integers are all in bytes.

Devices

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
size: integer,
description: string,
protocol: string,
blockSize: integer,
readOnly: boolean,
removable: boolean

Volumes

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
description: string,
blockSize: number,
blocks: number,
readOnly: boolean,
mounted: boolean,
mountPoint: boolean,
partitionType: string,
fs: string,
space: {
total: number,
available: number,
used: number
}

About

NodeJS Filesystem Utility

Resources

Stars

21 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Strip utm_, fbclid, gclid, etc. from all links on page\n(function() {\n var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',\n 'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',\n 'ref', 'ref_src', 'source', 'medium', 'campaign'];\n \n function cleanUrl(url) {\n try {\n var u = new URL(url, window.location.origin);\n var changed = false;\n trackingParams.forEach(function(p) {\n if (u.searchParams.has(p)) {\n u.searchParams.delete(p);\n changed = true;\n }\n });\n return changed ? u.toString() : url;\n } catch (e) {\n return url;\n }\n }\n \n function cleanLinks() {\n document.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n \n cleanLinks();\n \n var observer = new MutationObserver(function(mutations) {\n mutations.forEach(function(m) {\n m.addedNodes.forEach(function(node) {\n if (node.nodeType === 1) {\n if (node.tagName === 'A') cleanLinks();\n node.querySelectorAll('a[href]').forEach(function(a) {\n var clean = cleanUrl(a.href);\n if (clean !== a.href) a.href = clean;\n });\n }\n });\n });\n });\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "Remove Tracking Parameters from Links"); } } catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); } })(); (function(){ try { var __m = "youtube.com"; var __re = new RegExp('^' + "youtube\\.com" + '
Skip to content
This repository was archived by the owner on Aug 5, 2020. It is now read-only.

Repository files navigation

Node.js: fs-filesystem

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

npm versionTravis Build StatusWindows Build StatusCoverage StatusDependencies Status

Why?

Because sometimes your desktop applications need information about the filesystem (*cough* like on Windows *cough*)

Installation

npm install --save fs-filesystem

Native Dependencies

Bear in mind that this utility shells out to the machine, and thus requires the host to be able to run such commands. If any of the commands listed below are missing from your OS, the utility will throw a Command Failed: ... error. This shouldn't be a problem however since these are standard, core commands generally available on their respective distros (well, except maybe minimal Linux distros like Arch and Alpine), so you should be fine :)

  • Linux:df, fdisk, lsblk
  • MacOS:diskutil
  • Windows:wmic

API

Async

importfilesystemfrom'fs-filesystem';filesystem(filter,(err,result)=>{console.log('devices',result);});

filesystem( [ filter , ], callback )

// filesystem :: string|RegExp|function|undefined|null, function -> void

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices
  • callback {function}: Function following the common Node.js callback style, i.e. taking a (err, value) => ...

If only a function is provided to filesystem, the utility will assume that it is the callback function.

Wanna get rid of the callback? Try util.promisify for Node >=8, bluebird's Promise.promisify or universalify ;)

Sync

import{filesystemSync}from'fs-filesystem';constresult=filesystemSync(filter);console.log('devices',result);

filesystemSync( [ filter ] )

Remember, it's usually discouraged to use sync functions except when doing early setup!

// filesystemSync :: string|RegExp|function|undefined|null -> Object

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices

What Data Can I Expect?

fs-filesystem will return a hash object of all the devices available on the computer, whether networked, internal or external/removable. Their respective volumes are available as an array of volumes under the device.volumes property. Linux and MacOS users will be pleased with the amount of detail available - block size, partition type, filesystem, mounted, mount point, blocks, and more is available. Windows users fall on the short straw however with a much less rich output. This is because (a) the main maintainer of fs-filesystem has very little knowledge of DOS/PowerShell utilities and (b) there seems to be very little filesystem utilities available on Windows that do not require elevated privileges. So if you are a Windows DemiGod, feel free to enlighten us 🚀

Sample Outputs

MacOS

{
"disk1": {
"id": "disk1",
"node": "/dev/disk1",
"whole": true,
"parent": "disk1",
"name": null,
"size": 2000398934016,
"description": "APPLE HDD ST2000DM001",
"protocol": "SATA",
"blockSize": 512,
"removable": true,
"mounted": false,
"volumes": [
{
"id": "disk1s1",
"node": "/dev/disk1s1",
"whole": false,
"parent": "disk1",
"name": "EFI",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "EFI",
"fs": "FAT32",
"space": {
"total": 0,
"available": 0,
"used": 0
}
},
{
"id": "disk1s2",
"node": "/dev/disk1s2",
"whole": false,
"parent": "disk1",
"name": "Recovery HD",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "Apple_Boot",
"fs": "HFS+",
"space": {
"total": 0,
"available": 0,
"used": 0
}
}
]
}
}

Linux

{
"sda": {
"id": "sda",
"node": "/dev/sda",
"whole": true,
"parent": "sda",
"name": "sda",
"size": 250059350016,
"description": null,
"protocol": null,
"blockSize": 512,
"readOnly": false,
"removable": false,
"blocks": 488397168,
"volumes": [
{
"id": "sda2",
"node": "/dev/sda2",
"whole": false,
"parent": "sda",
"name": "sda2",
"description": "Linux filesystem",
"blockSize": 512,
"blocks": 455499776,
"readOnly": false,
"mounted": true,
"mountPoint": "/",
"partitionType": null,
"fs": "ext4",
"space": {
"total": 229421658112,
"available": 21887852544,
"used": 195856236544
},
"removable": false
},
{
"id": "sda1",
"node": "/dev/sda1",
"whole": false,
"parent": "sda",
"name": "sda1",
"description": "BIOS boot",
"blockSize": 512,
"blocks": 2048,
"readOnly": false,
"mounted": false,
"mountPoint": null,
"partitionType": null,
"fs": null,
"space": {
"total": null,
"available": null,
"used": null
},
"removable": false
}
]
}
}

Windows

{
"C:": {
"id": "C:",
"node": "C:",
"whole": true,
"parent": "C:",
"name": "C:",
"size": 22288527360,
"description": "Local Fixed Disk",
"protocol": null,
"blockSize": null,
"readOnly": null,
"removable": null,
"volumes": [
{
"id": "C:",
"node": "C:",
"whole": false,
"parent": "C:",
"name": null,
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": "C:",
"partitionType": null,
"fs": "NTFS",
"space": {
"total": 22288527360,
"available": 4928057344,
"used": 17360470016
}
}
]
}
}

Data Types

You can find a list of the types of each field below. Keep in mind that all fields besides whole are null by default, and that integers are all in bytes.

Devices

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
size: integer,
description: string,
protocol: string,
blockSize: integer,
readOnly: boolean,
removable: boolean

Volumes

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
description: string,
blockSize: number,
blocks: number,
readOnly: boolean,
mounted: boolean,
mountPoint: boolean,
partitionType: string,
fs: string,
space: {
total: number,
available: number,
used: number
}

About

NodeJS Filesystem Utility

Resources

Stars

21 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Auto-enable theater mode on YouTube\n(function() {\n function tryTheater() {\n var btn = document.querySelector('button[aria-label=\"Theater mode\"], ytd-player #player button[title=\"Theater mode\"]');\n if (btn && !btn.classList.contains('activated')) {\n btn.click();\n }\n }\n \n // Try immediately\n tryTheater();\n \n // Try after navigation (SPA)\n var lastUrl = location.href;\n setInterval(function() {\n if (location.href !== lastUrl) {\n lastUrl = location.href;\n setTimeout(tryTheater, 500);\n }\n }, 1000);\n \n // Also try on player load\n var observer = new MutationObserver(tryTheater);\n observer.observe(document.body, { childList: true, subtree: true });\n})();", "YouTube Theater Mode Default"); } } catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content
This repository was archived by the owner on Aug 5, 2020. It is now read-only.

Repository files navigation

Node.js: fs-filesystem

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

npm versionTravis Build StatusWindows Build StatusCoverage StatusDependencies Status

Why?

Because sometimes your desktop applications need information about the filesystem (*cough* like on Windows *cough*)

Installation

npm install --save fs-filesystem

Native Dependencies

Bear in mind that this utility shells out to the machine, and thus requires the host to be able to run such commands. If any of the commands listed below are missing from your OS, the utility will throw a Command Failed: ... error. This shouldn't be a problem however since these are standard, core commands generally available on their respective distros (well, except maybe minimal Linux distros like Arch and Alpine), so you should be fine :)

  • Linux:df, fdisk, lsblk
  • MacOS:diskutil
  • Windows:wmic

API

Async

importfilesystemfrom'fs-filesystem';filesystem(filter,(err,result)=>{console.log('devices',result);});

filesystem( [ filter , ], callback )

// filesystem :: string|RegExp|function|undefined|null, function -> void

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices
  • callback {function}: Function following the common Node.js callback style, i.e. taking a (err, value) => ...

If only a function is provided to filesystem, the utility will assume that it is the callback function.

Wanna get rid of the callback? Try util.promisify for Node >=8, bluebird's Promise.promisify or universalify ;)

Sync

import{filesystemSync}from'fs-filesystem';constresult=filesystemSync(filter);console.log('devices',result);

filesystemSync( [ filter ] )

Remember, it's usually discouraged to use sync functions except when doing early setup!

// filesystemSync :: string|RegExp|function|undefined|null -> Object

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices

What Data Can I Expect?

fs-filesystem will return a hash object of all the devices available on the computer, whether networked, internal or external/removable. Their respective volumes are available as an array of volumes under the device.volumes property. Linux and MacOS users will be pleased with the amount of detail available - block size, partition type, filesystem, mounted, mount point, blocks, and more is available. Windows users fall on the short straw however with a much less rich output. This is because (a) the main maintainer of fs-filesystem has very little knowledge of DOS/PowerShell utilities and (b) there seems to be very little filesystem utilities available on Windows that do not require elevated privileges. So if you are a Windows DemiGod, feel free to enlighten us 🚀

Sample Outputs

MacOS

{
"disk1": {
"id": "disk1",
"node": "/dev/disk1",
"whole": true,
"parent": "disk1",
"name": null,
"size": 2000398934016,
"description": "APPLE HDD ST2000DM001",
"protocol": "SATA",
"blockSize": 512,
"removable": true,
"mounted": false,
"volumes": [
{
"id": "disk1s1",
"node": "/dev/disk1s1",
"whole": false,
"parent": "disk1",
"name": "EFI",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "EFI",
"fs": "FAT32",
"space": {
"total": 0,
"available": 0,
"used": 0
}
},
{
"id": "disk1s2",
"node": "/dev/disk1s2",
"whole": false,
"parent": "disk1",
"name": "Recovery HD",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "Apple_Boot",
"fs": "HFS+",
"space": {
"total": 0,
"available": 0,
"used": 0
}
}
]
}
}

Linux

{
"sda": {
"id": "sda",
"node": "/dev/sda",
"whole": true,
"parent": "sda",
"name": "sda",
"size": 250059350016,
"description": null,
"protocol": null,
"blockSize": 512,
"readOnly": false,
"removable": false,
"blocks": 488397168,
"volumes": [
{
"id": "sda2",
"node": "/dev/sda2",
"whole": false,
"parent": "sda",
"name": "sda2",
"description": "Linux filesystem",
"blockSize": 512,
"blocks": 455499776,
"readOnly": false,
"mounted": true,
"mountPoint": "/",
"partitionType": null,
"fs": "ext4",
"space": {
"total": 229421658112,
"available": 21887852544,
"used": 195856236544
},
"removable": false
},
{
"id": "sda1",
"node": "/dev/sda1",
"whole": false,
"parent": "sda",
"name": "sda1",
"description": "BIOS boot",
"blockSize": 512,
"blocks": 2048,
"readOnly": false,
"mounted": false,
"mountPoint": null,
"partitionType": null,
"fs": null,
"space": {
"total": null,
"available": null,
"used": null
},
"removable": false
}
]
}
}

Windows

{
"C:": {
"id": "C:",
"node": "C:",
"whole": true,
"parent": "C:",
"name": "C:",
"size": 22288527360,
"description": "Local Fixed Disk",
"protocol": null,
"blockSize": null,
"readOnly": null,
"removable": null,
"volumes": [
{
"id": "C:",
"node": "C:",
"whole": false,
"parent": "C:",
"name": null,
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": "C:",
"partitionType": null,
"fs": "NTFS",
"space": {
"total": 22288527360,
"available": 4928057344,
"used": 17360470016
}
}
]
}
}

Data Types

You can find a list of the types of each field below. Keep in mind that all fields besides whole are null by default, and that integers are all in bytes.

Devices

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
size: integer,
description: string,
protocol: string,
blockSize: integer,
readOnly: boolean,
removable: boolean

Volumes

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
description: string,
blockSize: number,
blocks: number,
readOnly: boolean,
mounted: boolean,
mountPoint: boolean,
partitionType: string,
fs: string,
space: {
total: number,
available: number,
used: number
}

About

NodeJS Filesystem Utility

Resources

Stars

21 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Remove or un-stick sticky/fixed headers that block content\n(function() {\n function unstick() {\n document.querySelectorAll('header, nav, [role=\"banner\"], .header, .navbar, .sticky, .fixed-top, [style*=\"position: fixed\"], [style*=\"position:sticky\"]').forEach(function(el) {\n if (el.style.position === 'fixed' || el.style.position === 'sticky' || \n getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {\n el.style.position = 'static';\n el.style.top = 'auto';\n el.style.zIndex = 'auto';\n }\n });\n }\n \n unstick();\n \n var observer = new MutationObserver(unstick);\n observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });\n})();", "Kill Sticky Headers"); } } catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); } })(); (function(){ try { var __m = "*"; var __re = new RegExp('^' + ".*" + '
Skip to content
This repository was archived by the owner on Aug 5, 2020. It is now read-only.

Repository files navigation

Node.js: fs-filesystem

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

npm versionTravis Build StatusWindows Build StatusCoverage StatusDependencies Status

Why?

Because sometimes your desktop applications need information about the filesystem (*cough* like on Windows *cough*)

Installation

npm install --save fs-filesystem

Native Dependencies

Bear in mind that this utility shells out to the machine, and thus requires the host to be able to run such commands. If any of the commands listed below are missing from your OS, the utility will throw a Command Failed: ... error. This shouldn't be a problem however since these are standard, core commands generally available on their respective distros (well, except maybe minimal Linux distros like Arch and Alpine), so you should be fine :)

  • Linux:df, fdisk, lsblk
  • MacOS:diskutil
  • Windows:wmic

API

Async

importfilesystemfrom'fs-filesystem';filesystem(filter,(err,result)=>{console.log('devices',result);});

filesystem( [ filter , ], callback )

// filesystem :: string|RegExp|function|undefined|null, function -> void

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices
  • callback {function}: Function following the common Node.js callback style, i.e. taking a (err, value) => ...

If only a function is provided to filesystem, the utility will assume that it is the callback function.

Wanna get rid of the callback? Try util.promisify for Node >=8, bluebird's Promise.promisify or universalify ;)

Sync

import{filesystemSync}from'fs-filesystem';constresult=filesystemSync(filter);console.log('devices',result);

filesystemSync( [ filter ] )

Remember, it's usually discouraged to use sync functions except when doing early setup!

// filesystemSync :: string|RegExp|function|undefined|null -> Object

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices

What Data Can I Expect?

fs-filesystem will return a hash object of all the devices available on the computer, whether networked, internal or external/removable. Their respective volumes are available as an array of volumes under the device.volumes property. Linux and MacOS users will be pleased with the amount of detail available - block size, partition type, filesystem, mounted, mount point, blocks, and more is available. Windows users fall on the short straw however with a much less rich output. This is because (a) the main maintainer of fs-filesystem has very little knowledge of DOS/PowerShell utilities and (b) there seems to be very little filesystem utilities available on Windows that do not require elevated privileges. So if you are a Windows DemiGod, feel free to enlighten us 🚀

Sample Outputs

MacOS

{
"disk1": {
"id": "disk1",
"node": "/dev/disk1",
"whole": true,
"parent": "disk1",
"name": null,
"size": 2000398934016,
"description": "APPLE HDD ST2000DM001",
"protocol": "SATA",
"blockSize": 512,
"removable": true,
"mounted": false,
"volumes": [
{
"id": "disk1s1",
"node": "/dev/disk1s1",
"whole": false,
"parent": "disk1",
"name": "EFI",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "EFI",
"fs": "FAT32",
"space": {
"total": 0,
"available": 0,
"used": 0
}
},
{
"id": "disk1s2",
"node": "/dev/disk1s2",
"whole": false,
"parent": "disk1",
"name": "Recovery HD",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "Apple_Boot",
"fs": "HFS+",
"space": {
"total": 0,
"available": 0,
"used": 0
}
}
]
}
}

Linux

{
"sda": {
"id": "sda",
"node": "/dev/sda",
"whole": true,
"parent": "sda",
"name": "sda",
"size": 250059350016,
"description": null,
"protocol": null,
"blockSize": 512,
"readOnly": false,
"removable": false,
"blocks": 488397168,
"volumes": [
{
"id": "sda2",
"node": "/dev/sda2",
"whole": false,
"parent": "sda",
"name": "sda2",
"description": "Linux filesystem",
"blockSize": 512,
"blocks": 455499776,
"readOnly": false,
"mounted": true,
"mountPoint": "/",
"partitionType": null,
"fs": "ext4",
"space": {
"total": 229421658112,
"available": 21887852544,
"used": 195856236544
},
"removable": false
},
{
"id": "sda1",
"node": "/dev/sda1",
"whole": false,
"parent": "sda",
"name": "sda1",
"description": "BIOS boot",
"blockSize": 512,
"blocks": 2048,
"readOnly": false,
"mounted": false,
"mountPoint": null,
"partitionType": null,
"fs": null,
"space": {
"total": null,
"available": null,
"used": null
},
"removable": false
}
]
}
}

Windows

{
"C:": {
"id": "C:",
"node": "C:",
"whole": true,
"parent": "C:",
"name": "C:",
"size": 22288527360,
"description": "Local Fixed Disk",
"protocol": null,
"blockSize": null,
"readOnly": null,
"removable": null,
"volumes": [
{
"id": "C:",
"node": "C:",
"whole": false,
"parent": "C:",
"name": null,
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": "C:",
"partitionType": null,
"fs": "NTFS",
"space": {
"total": 22288527360,
"available": 4928057344,
"used": 17360470016
}
}
]
}
}

Data Types

You can find a list of the types of each field below. Keep in mind that all fields besides whole are null by default, and that integers are all in bytes.

Devices

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
size: integer,
description: string,
protocol: string,
blockSize: integer,
readOnly: boolean,
removable: boolean

Volumes

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
description: string,
blockSize: number,
blocks: number,
readOnly: boolean,
mounted: boolean,
mountPoint: boolean,
partitionType: string,
fs: string,
space: {
total: number,
available: number,
used: number
}

About

NodeJS Filesystem Utility

Resources

Stars

21 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages

, 'i'); if (__m === '*' || __re.test(location.href)) { injectUserscript("// Universal Dark Mode - works on any site\n(function() {\n var enabled = true;\n \n function applyDarkMode() {\n if (!enabled) return;\n \n // Create style element if it doesn't exist\n var style = document.getElementById('universal-dark-mode-style');\n if (!style) {\n style = document.createElement('style');\n style.id = 'universal-dark-mode-style';\n document.head.appendChild(style);\n }\n \n // Dark mode CSS - inverts colors but preserves images/video\n style.textContent = '\n /* Invert everything except media */\n html {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #1a1a2e !important;\n }\n \n /* Restore images, videos, iframes, canvas */\n img, video, iframe, canvas, svg, picture, [style*=\"background-image\"] {\n filter: invert(1) hue-rotate(180deg) !important;\n }\n \n /* Preserve specific elements that should not be inverted */\n .no-dark-mode, .no-dark-mode *,\n [data-theme=\"light\"], [data-theme=\"light\"],\n .ace_editor, .ace_editor *,\n .CodeMirror, .CodeMirror *,\n .monaco-editor, .monaco-editor *,\n .markdown-body pre, .markdown-body pre *,\n .highlight, .highlight *,\n pre code, pre code * {\n filter: none !important;\n }\n \n /* Fix common UI elements */\n .modal, .popup, .dropdown-menu, .tooltip, .popover {\n filter: invert(1) hue-rotate(180deg) !important;\n background: #2d2d44 !important;\n border-color: #444 !important;\n }\n \n /* Scrollbars */\n ::-webkit-scrollbar { background: #1a1a2e !important; }\n ::-webkit-scrollbar-thumb { background: #444 !important; }\n ::-webkit-scrollbar-thumb:hover { background: #555 !important; }\n \n /* Selection */\n ::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }\n ';\n }\n \n function removeDarkMode() {\n var style = document.getElementById('universal-dark-mode-style');\n if (style) style.remove();\n }\n \n // Toggle with Alt+Shift+D\n document.addEventListener('keydown', function(e) {\n if (e.altKey && e.shiftKey && e.key === 'D') {\n e.preventDefault();\n enabled = !enabled;\n if (enabled) {\n applyDarkMode();\n console.log('[Universal Dark Mode] Enabled');\n } else {\n removeDarkMode();\n console.log('[Universal Dark Mode] Disabled');\n }\n }\n });\n \n // Apply on load\n applyDarkMode();\n \n // Re-apply on dynamic content\n var observer = new MutationObserver(function(mutations) {\n if (enabled && !document.getElementById('universal-dark-mode-style')) {\n applyDarkMode();\n }\n });\n observer.observe(document.head, { childList: true });\n \n console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');\n})();", "Universal Dark Mode"); } } catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); } })(); })();
Skip to content
This repository was archived by the owner on Aug 5, 2020. It is now read-only.

Repository files navigation

Node.js: fs-filesystem

fs-filesystem allows you to read the state of the filesystem of the host on which it is run. It returns information about both the devices and the partitions (volumes) of the system.

npm versionTravis Build StatusWindows Build StatusCoverage StatusDependencies Status

Why?

Because sometimes your desktop applications need information about the filesystem (*cough* like on Windows *cough*)

Installation

npm install --save fs-filesystem

Native Dependencies

Bear in mind that this utility shells out to the machine, and thus requires the host to be able to run such commands. If any of the commands listed below are missing from your OS, the utility will throw a Command Failed: ... error. This shouldn't be a problem however since these are standard, core commands generally available on their respective distros (well, except maybe minimal Linux distros like Arch and Alpine), so you should be fine :)

  • Linux:df, fdisk, lsblk
  • MacOS:diskutil
  • Windows:wmic

API

Async

importfilesystemfrom'fs-filesystem';filesystem(filter,(err,result)=>{console.log('devices',result);});

filesystem( [ filter , ], callback )

// filesystem :: string|RegExp|function|undefined|null, function -> void

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices
  • callback {function}: Function following the common Node.js callback style, i.e. taking a (err, value) => ...

If only a function is provided to filesystem, the utility will assume that it is the callback function.

Wanna get rid of the callback? Try util.promisify for Node >=8, bluebird's Promise.promisify or universalify ;)

Sync

import{filesystemSync}from'fs-filesystem';constresult=filesystemSync(filter);console.log('devices',result);

filesystemSync( [ filter ] )

Remember, it's usually discouraged to use sync functions except when doing early setup!

// filesystemSync :: string|RegExp|function|undefined|null -> Object

  • filter {string|RegExp|function|undefined|null}: A filter for which devices should be returned. If the filter is a string or RegExp, fs-filesystem will match the device keys against it. If the filter is left undefined or null, fs-filesystem will return all of the devices. If the filter is a function, it will receive (device, key, devices) as arguments.
    • device {Object}: The device to filter
    • key {string}: The key of the device (also known as id)
    • devices {Object}: The hash of all devices

What Data Can I Expect?

fs-filesystem will return a hash object of all the devices available on the computer, whether networked, internal or external/removable. Their respective volumes are available as an array of volumes under the device.volumes property. Linux and MacOS users will be pleased with the amount of detail available - block size, partition type, filesystem, mounted, mount point, blocks, and more is available. Windows users fall on the short straw however with a much less rich output. This is because (a) the main maintainer of fs-filesystem has very little knowledge of DOS/PowerShell utilities and (b) there seems to be very little filesystem utilities available on Windows that do not require elevated privileges. So if you are a Windows DemiGod, feel free to enlighten us 🚀

Sample Outputs

MacOS

{
"disk1": {
"id": "disk1",
"node": "/dev/disk1",
"whole": true,
"parent": "disk1",
"name": null,
"size": 2000398934016,
"description": "APPLE HDD ST2000DM001",
"protocol": "SATA",
"blockSize": 512,
"removable": true,
"mounted": false,
"volumes": [
{
"id": "disk1s1",
"node": "/dev/disk1s1",
"whole": false,
"parent": "disk1",
"name": "EFI",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "EFI",
"fs": "FAT32",
"space": {
"total": 0,
"available": 0,
"used": 0
}
},
{
"id": "disk1s2",
"node": "/dev/disk1s2",
"whole": false,
"parent": "disk1",
"name": "Recovery HD",
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": null,
"partitionType": "Apple_Boot",
"fs": "HFS+",
"space": {
"total": 0,
"available": 0,
"used": 0
}
}
]
}
}

Linux

{
"sda": {
"id": "sda",
"node": "/dev/sda",
"whole": true,
"parent": "sda",
"name": "sda",
"size": 250059350016,
"description": null,
"protocol": null,
"blockSize": 512,
"readOnly": false,
"removable": false,
"blocks": 488397168,
"volumes": [
{
"id": "sda2",
"node": "/dev/sda2",
"whole": false,
"parent": "sda",
"name": "sda2",
"description": "Linux filesystem",
"blockSize": 512,
"blocks": 455499776,
"readOnly": false,
"mounted": true,
"mountPoint": "/",
"partitionType": null,
"fs": "ext4",
"space": {
"total": 229421658112,
"available": 21887852544,
"used": 195856236544
},
"removable": false
},
{
"id": "sda1",
"node": "/dev/sda1",
"whole": false,
"parent": "sda",
"name": "sda1",
"description": "BIOS boot",
"blockSize": 512,
"blocks": 2048,
"readOnly": false,
"mounted": false,
"mountPoint": null,
"partitionType": null,
"fs": null,
"space": {
"total": null,
"available": null,
"used": null
},
"removable": false
}
]
}
}

Windows

{
"C:": {
"id": "C:",
"node": "C:",
"whole": true,
"parent": "C:",
"name": "C:",
"size": 22288527360,
"description": "Local Fixed Disk",
"protocol": null,
"blockSize": null,
"readOnly": null,
"removable": null,
"volumes": [
{
"id": "C:",
"node": "C:",
"whole": false,
"parent": "C:",
"name": null,
"description": null,
"blockSize": null,
"blocks": null,
"readOnly": null,
"mounted": true,
"mountPoint": "C:",
"partitionType": null,
"fs": "NTFS",
"space": {
"total": 22288527360,
"available": 4928057344,
"used": 17360470016
}
}
]
}
}

Data Types

You can find a list of the types of each field below. Keep in mind that all fields besides whole are null by default, and that integers are all in bytes.

Devices

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
size: integer,
description: string,
protocol: string,
blockSize: integer,
readOnly: boolean,
removable: boolean

Volumes

id: string,
node: string,
whole: boolean,
parent: string,
name: string,
description: string,
blockSize: number,
blocks: number,
readOnly: boolean,
mounted: boolean,
mountPoint: boolean,
partitionType: string,
fs: string,
space: {
total: number,
available: number,
used: number
}

About

NodeJS Filesystem Utility

Resources

Stars

21 stars

Watchers

1 watching

Forks

Releases

Packages

Used by

Contributors

Languages