faucet-pipeline-js

faucet-pipeline-js version history ================================== v3.0.2 ------ _2026-03-06_ maintenance release to update dependencies; no significant changes v3.0.1 ------ _2023-11-09_ maintenance release to update dependencies; no significant changes v3.0.0 ------ _2023-01-16_ notable changes for end users: * switched to ESM as default output format * removed deprecated `sourcemap` option (long superseded by `sourcemaps`) * removed support for custom file extensions notable changes for developers: * removed support for virtual bundles v2.1.8 ------ _2022-03-08_ maintenance release to update dependencies; no significant changes v2.1.7 ------ _2020-11-20_ maintenance release to update dependencies; no significant changes v2.1.6 ------ _2020-06-15_ maintenance release to update dependencies; no significant changes v2.1.5 ------ _2020-05-22_ notable changes for end users: * fixed a compatibility issues with CommonJS modules * silenced a warning when transpiling ESNext no significant changes for developers (skipping v2.1.4 due to a technical glitch in the release process) v2.1.3 ------ _2020-05-15_ maintenance release to update dependencies; no significant changes v2.1.2 ------ _2020-04-08_ maintenance release to update dependencies; no significant changes v2.1.1 ------ _2020-03-17_ fixed outdated dependency references (regression in v2.1.0) v2.1.0 ------ _2020-03-16_ maintenance release to update dependencies; no significant changes v2.0.10 ------- _2019-11-26_ maintenance release to update dependencies; no significant changes v2.0.9 ------ _2019-10-28_ maintenance release to update dependencies; no significant changes v2.0.8 ------ _2019-09-02_ maintenance release to update dependencies; no significant changes v2.0.7 ------ _2019-08-06_ notable changes for end users: * fixed potential race condition in conjunction with adjacent plugins v2.0.6 ------ _2019-06-21_ notable changes for end users: * fixed module resolution to prefer `jsnext:main` over `main` if present this ensures that ESM is used instead of legacy module formats (while `jsnext:main` is considered deprecated, it's still being used in the wild) no significant changes for developers v2.0.5 ------ _2019-06-05_ maintenance release to update dependencies; no significant changes v2.0.4 ------ _2019-05-10_ maintenance release to update dependencies; no significant changes v2.0.3 ------ _2019-04-11_ maintenance release to update dependencies; no significant changes v2.0.2 ------ _2019-04-02_ maintenance release to update dependencies; no significant changes v2.0.1 ------ _2019-03-15_ maintenance release to update dependencies; no significant changes v2.0.0 ------ _2019-02-18_ notable changes for end users: * extended compacting options if compacting is activated, bundles can now opt into varying levels of minification via `compact: minify` or `compact: mangle` * added support for JSX fragments `<>…</>` shorthand syntax can now be configured via `jsx.fragment` (alongside `jsx.pragma`) * removed `global` shim introducing this was premature in the first place: it might not be officially called `global` after all, but faucet-pipeline is not in the business of polyfilling anyway this should be handled at the application level if necessary, for example by creating and importing (early on) a module like this: ```javascript if(typeof global === "undefined" && typeof window !== "undefined") { window.global = window; } ``` * renamed default identifier for ECMAScript module format: `es` → `esm` `es` remains supported for backwards compatibility though * dropped Node 6 compatibility April 2019 marks the end of life for this LTS version, so it should soon be phased out by users (while most functionality - namely anything but JSX - remains compatible for now, we no longer offer any guarantees in that regard) notable changes for developers: * renamed configuration property for source maps: `sourcemap` → `sourcemaps` v1.1.1 ------ _2018-11-29_ notable changes for end users: * fixed change detection in watch mode if multiple files were altered simultaneously no significant changes for developers v1.1.0 ------ _2018-11-07_ no significant changes for end users notable changes for developers: * added support for virtual bundles, using strings rather than files as entry point and not automatically writing bundles to disk (programmatic API only) * improved support for compiling bundles programmatically