Search Results for "package"

...For testing and debugging, a file can be built into a temporary directory and executed with full source maps support. Some packages may need some extra options for ncc support in order to better work with the static analysis. See package-support.md for some common packages and their usage with ncc.

webpack is a module bundler that is primarily used for bundling JavaScript files for usage in a browser, though it can also transform, bundle, or package just about any resource or asset, including images and styles. webpack packs many modules into a few bundled assets. It can bundle ES Modules, CommonJS, and AMD modules, and create a single bundle or multiple chunks through code-splitting that are asynchronously loaded at runtime. It supports all browsers that are ES5-compliant, has a rich plugin interface that makes it very flexible, and enables the use of loaders to preprocess files.

closure-compiler-js packages Google’s Closure Compiler so it runs under JavaScript (e.g., Node.js) instead of a JVM, making advanced JS optimization accessible in more build pipelines. You get the same aggressive whole-program optimizations—dead-code elimination, property renaming, inlining, and cross-module motion—delivered via a JS API and CLI. Because it’s the compiler you know, it also honors Closure type annotations and JSDoc, enabling type-aware rewrites that shrink bundles without...

...Use it as a part of your asset packager to compile templates ahead of time or include it in your browser to handle dynamic templates. If you're developing with Node.js, just use NPM to add the Hogan package. Hogan.js was developed against the mustache test suite, so everything that holds true for templates is also the case for hogan.js. That means you get variables, sections, lambdas, partials, filters, and everything else you've come to expect from mustache templating, only much, much faster. Use hogan.compile() to precompile your templates into vanilla JS. ...