nw-global-nav-asset-shim
Advanced tools
Serve app-site assets from your node app.
This is meant to simplify development of node apps outside of
dev-vagrant only. This module should not be used in production.
npm i --save nw-global-nav-asset-shim
var app = require(express)()
if (process.env.NODE_ENV === 'development') {
var shim = require('nw-global-nav-asset-shim')
shim({ appsitePath: '/my/dev/app-site' }, app)
}
Shims the following asset routes:
/css
/js
/global-styles
When consuming global-nav (via something like nw-nerdlayoutjs) you get a
payload used as the layout for your app. Parts of the layout reference global
assets that make up things like the global header and footer styles and js. If
you want to run your node app outside of dev-vagrant you'll need to serve
these assets yourself so something like localhost:3000/css/bundle.min.css
resolves correctly. These assets live in your app-site clone, so this shim
just serves from your local clone at the expected routes (see above).
FAQs
Shims global-nav asset routes.
We found that nw-global-nav-asset-shim demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
A malicious npm package disguised as a WhatsApp client is exploiting authentication flows with a remote kill switch to exfiltrate data and destroy files.
Security News
PyPI now supports digital attestations, enhancing security and trust by allowing package maintainers to verify the authenticity of Python packages.
Security News
GitHub removed 27 malicious pull requests attempting to inject harmful code across multiple open source repositories, in another round of low-effort attacks.