public interface JSBundleProcessor
NPMRegistry to track them.
There can be several JSBundleProcessors deployed inside one portal if
necessary. This allows the deployment of OSGi bundles with different
structures containing the NPM packages.
By default, the portal is bundled with a default JSBundleProcessor
implemented by com.liferay.frontend.js.loader.modules.extender.internal.npm.flat.FlatNPMBundleProcessor,
which looks for NPM packages inside the
META-INF/resources/node_modules folder.
| Modifier and Type | Method and Description |
|---|---|
JSBundle |
process(org.osgi.framework.Bundle bundle)
Returns a JS Bundle filled with the description of the NPM packages or
modules found in the given bundle.
|
JSBundle process(org.osgi.framework.Bundle bundle)
null.
This method is invoked by the NPMRegistry whenever a new OSGi
bundle is deployed to the portal.
bundle - the handle to the OSGi bundle being deployednull if no NPM
packages or modules were found