Registry / web-framework / web-app-manifest-loader

web-app-manifest-loader

JSON →
library0.1.1jsnpmunverified

Webpack loader that resolves image paths in the `icons` and `splash_screens` fields of a Web App Manifest. Version 0.1.1 is current, last released several years ago with no active maintenance. This loader delegates to other loaders (e.g., file-loader) to handle image files. Unlike alternatives that require manual image processing, it automates asset management within manifests. It is deprecated in favor of modern webpack 5 asset modules and direct imports, as it is no longer actively developed.

npm install web-app-manifest-loader
INSTALL
IMPORT
SIG · WEB-APP-MANIFEST-L
W
web-app-manifest-loader
web-frameworkjavascriptv0.1.1
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
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 18226 runs
build_error
glibc
node 18226 runs
build_error
Code
Verified usage

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

default
module.exports = require('web-app-manifest-loader')
import webAppManifestLoader from 'web-app-manifest-loader'
This is a webpack loader, not imported in application code. Use in webpack config module.rules.
Webpack rule
{ test: /manifest.json$/, loader: 'file-loader?name=manifest.json!web-app-manifest-loader' }
{ test: /manifest.json$/, use: 'web-app-manifest-loader' }
Loader must be chained with file-loader; using alone won't output the manifest file.
require in app code
require('./manifest.json')
import manifest from './manifest.json'
Works with both, but require is traditional for webpack 1/2.

Shows webpack config chaining file-loader and web-app-manifest-loader, and application code requiring the manifest.

// webpack.config.js module.exports = { entry: './src/index.js', output: { filename: 'bundle.js' }, module: { rules: [ { test: /\.json$/, use: [ { loader: 'file-loader', options: { name: 'manifest.[ext]' } }, { loader: 'web-app-manifest-loader' } ] } ] } }; // manifest.json (in src/) { "name": "App", "icons": [{ "src": "./icon-512.png", "sizes": "512x512", "type": "image/png" }] } // src/index.js const manifest = require('./manifest.json'); console.log(manifest); // resolved with webpack asset paths
Debug
Known issues
deprecatedPackage is no longer actively maintained; last release was years ago.
fix
Consider using webpack 5 asset modules or inline image imports in manifest.
affects: >=0.0.0
gotchaLoader only processes JSON files; if you use a different extension or custom format, it won't work.
fix
Ensure your manifest file matches the test pattern and is valid JSON.
affects: >=0.0.0
gotchaMust be chained with a file-output loader like file-loader; alone it doesn't emit the manifest file.
fix
Add file-loader to the loader chain as shown in the quickstart.
affects: >=0.0.0
Errors
Common errors & fixes
Module not found: Error: Can't resolve '/path/to/icon.png' in '...'
Image path in manifest not found relative to manifest file location.
fix
Use relative paths starting with './' in manifest.json, e.g., './images/icon.png'.
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file.
Missing loader for JSON files or wrong chain order.
fix
Add web-app-manifest-loader and file-loader to webpack config as shown in quickstart.
Upgrade
Version history
0.1.1latest on npm
Audit
Dependencies
file-loaderoptionalcommonly chained to output manifest file
Agent activity
13 hits · last 30 days
node
10
OpenAI (training)
2
Resources
web-app-manifest-loader — npm install web-app-manifest-loader · libregistry