Registry / http-networking / path-loader

path-loader

JSON →
library0.1.1jsnpmunverified

path-loader is a JavaScript utility library designed to provide a unified API for loading content from both file paths and URLs, operating seamlessly across Node.js and browser environments. It currently supports `http`/`https` loaders for remote resources (default in browsers and for URLs in Node.js) and a `file` loader specifically for Node.js. While the README mentions future plans for a pluggable infrastructure, the package has not seen active development since its last release, version 1.0.12, in August 2016. Its release cadence is effectively inactive. The library differentiates itself by abstracting away environment-specific data loading mechanisms (e.g., XMLHttpRequest/fetch in browsers, `fs` or `http` modules in Node.js) behind a single `load` interface, utilizing `superagent` for AJAX functionality and `native-promise-only` for Promise polyfilling.

http-networkingserialization
npm install path-loader
github ↗package ↗
INSTALL
IMPORT
SIG · PATH-LOADER
P
path-loader
http-networkingjavascriptv0.1.1
Install
—
Import
—
Disk
—
Pass rate
0/ 6
Env Coverage0 / 6
glibc
18–22
musl
18–22
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18–226 runs
build_error
glibc
node 18–226 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

loader
✓ const loader = require('path-loader');
✗ import loader from 'path-loader';
Primarily designed for CommonJS; direct ESM import not officially supported. For browser, it exposes a global `pathLoader`.
pathLoader (global)
✓ <!-- In HTML after script tag --> <script src="path-loader.js"></script> <script> pathLoader.load('https://example.com/data.json') .then(console.log) .catch(console.error); </script>
When used directly in a browser via a `<script>` tag, the utility is exposed as a global `pathLoader` object.
load
✓ const { load } = require('path-loader');
✗ const load = require('path-loader').load;
The `loader` object returned by `require('path-loader')` has a `load` method. Destructuring can be used.

Demonstrates loading JSON content from a remote URL (works in browser and Node.js) and a local file (Node.js only) using the unified `loader.load` API.

const loader = require('path-loader'); // Example: Loading content from a remote URL loader.load('https://jsonplaceholder.typicode.com/posts/1') .then(function (res) { console.log('Successfully loaded remote data:'); console.log(JSON.parse(res.text)); }) .catch(function (err) { console.error('Error loading remote data:', err.message); }); // Example: Loading a local file (Node.js only) // This will likely fail if the file does not exist or permissions are incorrect. // In a real application, replace 'package.json' with a valid local path. if (typeof window === 'undefined') { // Check if running in Node.js loader.load('./package.json') .then(function (res) { console.log('\nSuccessfully loaded local file:'); console.log(JSON.parse(res.text)); }) .catch(function (err) { console.error('\nError loading local file:', err.message); }); }
Debug
Known issues
gotchaThe `file` loader, which is used by default in Node.js for local paths, is explicitly not supported in browser environments and will throw an error if attempted.
fix
In browser environments, only use `http:` or `https:` URLs. To load local files, consider a web server to serve them via HTTP or alternative browser-specific file APIs.
affects: >=1.0.0
breakingThe package has been effectively abandoned since its last update in August 2016. This means it may not be compatible with newer Node.js versions, browser APIs, or modern JavaScript features. Its dependencies (`superagent`, `native-promise-only`) may also contain unpatched security vulnerabilities or have breaking changes in their own development, potentially leading to supply chain issues.
fix
For new projects, consider modern alternatives like `node-fetch` (Node.js) or the native `fetch` API (browser) for HTTP requests, and `fs.promises` (Node.js) for file system operations. If you must use `path-loader`, thorough security audits and compatibility testing are essential.
affects: >=1.0.0
deprecatedThe primary API pattern is CommonJS `require()`. While UMD builds are provided for browsers, modern module systems (ESM) are not natively supported, making integration into contemporary build pipelines less straightforward.
fix
For Node.js ESM projects, you might need a wrapper or dynamic import (`import('path-loader')`) if direct `require` is problematic. For browser ESM, a bundler like Webpack or Rollup would be necessary, but consider migrating to modern `fetch` or a actively maintained HTTP client library.
affects: >=1.0.0
Errors
Common errors & fixes
Error: The file loader is not supported in the browser environment.
Attempting to use `loader.load()` with a local file path (e.g., `./data.json` or `file:///path/to/data.txt`) in a browser environment.
fix
Ensure that `path-loader` is only used with `http:` or `https:` URLs when running in a browser. Local files must be served via a web server.
TypeError: loader.load is not a function
This usually occurs if `path-loader` was not correctly `require`d, or if an older, incompatible version was installed that lacked the `load` method, or if trying to call `load` directly on the `path-loader` module instead of the returned `loader` object.
fix
Verify that `const loader = require('path-loader');` is used and then call `loader.load(path)`. Check `package.json` to ensure `path-loader` is listed as a dependency and `npm install` has been run.
UnhandledPromiseRejectionWarning: (node:XXXXX) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
The `loader.load()` method returns a Promise, and if an error occurs during loading (e.g., file not found, network error), the promise will reject without an attached `.catch()` handler.
fix
Always attach a `.catch()` block to your `loader.load()` calls to handle potential errors gracefully. Example: `loader.load(path).then(res => ...).catch(err => console.error(err));`
Upgrade
Version history
0.1.1latest on npm
Audit
Dependencies
native-promise-onlyrequiredUsed to shim in Promises support for environments that lack them.
superagentrequiredProvides AJAX capabilities for both browser and Node.js environments.
Agent activity
2 hits · last 30 days
node
2
Resources
githubhttps://github.com/whitlockjc/path-loader ↗
packagehttps://www.npmjs.com/package/path-loader ↗
path-loader — npm install path-loader · libregistry