Should the scheme modules be stored independently on disk?

[TomStrepsil]

The webpack package has some in-line code in string templates, since the scripts must be generated with replacements; webpack does not accept dynamic values at build time:

here:

return `import pointCut from "${SCHEME}:${POINT_CUTS}:/${name}";
import * as joinPoint from "${path}";
const variants = import.meta.webpackContext("${directory}", { recursive: true, regExp: ${regex} });
export default pointCut({ joinPoint, variants });`;

and here:

return `import togglePoint from "${togglePointModule}";
import handler from "${toggleHandler}";
export default (rest) => handler({ togglePoint, ...rest });`;

It'd perhaps be nice to have this code as templated javascript, to perhaps allow rudimentary unit testing, and for them to perhaps move independently of the Webpack plugin itself.

However, the interface is coupled closely to the Webpack plugin code itself, so may be unlikely to change.

Perhaps would be of more use as new scheme modules or variations of such are needed by some new functionality in future.

plop is a tool that could be used for this purpose?