Create a pipeline to analyze a JavaScript/TypeScript-based app, including webpacked JS

When I use JavaScript in an application, I have a few typical configurations and contexts:

**At development time:**
- I will use npm with a package.json (or more rarely bower) to describe my top level dependencies, and I will save a package-lock.json (or yarn.lock if I use yarn) that contains a frozen set of resolved package deps.
- I may have a directory with nested node_modules that contain my actual dependencies
- I may use webpack to combine one or more libraries together (typically for use in the web browser for frontend code) or some other "minifying" or bundling tool
- I may use TypeScript as source code and transpile it to JS, or I may use other transpilers such as Babel.

**At run time:**
- I may deploy some `node_modules` as-is (typical for a node-based server-side application) or as resources in some other deployed artifacts (seen sometimes in Java)
- I will deploy the transpiled/webpacked code together with a possible .jsmap map file that may contain the original sources and the mapping of transpiled symbols back to their source code equivalent

**My problem** is to find which subset of the devel codebase (the From side) has been deployed (the To side) knowing that the deployed JS may be:

- remixed, minified, transpiled or webpacked
- copied as-is
- The same can be said for JS and CSS, and CSS could be transpiled from SCSS and/or Compass