Registry / devops / gatsby-plugin-well-known

gatsby-plugin-well-known

JSON →
library1.0.0jsnpmunverified

Gatsby plugin (v1.0.0) that copies files from src/well-known to the .well-known directory during builds. Lightweight and purpose-built for hosting security/auth files (e.g., assetlinks.json, apple-app-site-association). Stable release with no known issues, passive maintenance. Unlike manual copy tasks, it integrates directly with Gatsby's build lifecycle.

devops
npm install gatsby-plugin-well-known
package ↗
INSTALL
IMPORT
SIG · GATSBY-PLUGIN-WELL
G
gatsby-plugin-well-known
devopsjavascriptv1.0.0
harness data pending
Install & Compatibility
Where this runs

No compatibility data collected yet for this library.

Code
Verified usage

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

gatsby-plugin-well-known
✓ plugins: ['gatsby-plugin-well-known']
✗ plugins: [{ resolve: 'gatsby-plugin-well-known', options: { /* any options */ } }]
Plugin takes no options. Use simple string in gatsby-config.

Add the plugin to your Gatsby site config. Ensure src/well-known exists.

// gatsby-config.js module.exports = { plugins: ['gatsby-plugin-well-known'] }
Debug
Known issues
gotchaPlugin copies files from src/well-known on every build. If you delete a file from src/well-known, it will NOT be removed from the public/.well-known directory.
fix
Manually clean public/.well-known or implement a prebuild script.
affects: >=1.0.0
gotchaPlugin only copies files at build time. For development (gatsby develop), files are not copied.
fix
Use gatsby build to see .well-known in output, or configure webpack to serve from src/well-known.
affects: >=1.0.0
deprecatedThis plugin may be considered passive maintenance; no new features are expected.
fix
Consider alternative solutions if more advanced directory copying is needed.
affects: >=1.0.0
Errors
Common errors & fixes
Error: The plugin gatsby-plugin-well-known is not a valid plugin
Plugin not installed or typo in gatsby-config.
fix
npm install gatsby-plugin-well-known and ensure correct spelling in plugins array.
ENOENT: no such file or directory, open 'src/well-known/somefile'
Source directory or file missing.
fix
Create src/well-known directory and add files you want copied.
File not copied to .well-known
Running gatsby develop instead of gatsby build.
fix
Use gatsby build to generate static files.
Upgrade
Version history
1.0.0latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
4 hits · last 30 days
node
4
Resources
packagegatsby-plugin-well-known ↗
gatsby-plugin-well-known — npm install gatsby-plugin-well-known · libregistry