@pushwoosh/frontend-builder-engine 3.0.1 → 3.1.0

package/lib/babel.application.config.js

@@ -1,26 +1,47 @@
+// Every preset and plugin below is resolved against this file instead of being
+// named as a bare specifier. Babel resolves bare names relative to the config
+// that declares them — i.e. the consuming project's babel.config.js — and npm
+// keeps our @babel/* copies nested under the engine whenever the consumer's
+// tree holds a conflicting version, which makes them invisible from there.
+const fromEngine = (name) => require.resolve(name);
+
+// Same reasoning for the helper runtime, via absoluteRuntime below. Passing our
+// own version matters too: the plugin defaults to `version: "7.0.0-beta.0"` and
+// silently inlines every helper it thinks that version lacks, instead of
+// importing it.
+const runtimeVersion = require('@babel/runtime/package.json').version;
+
+const { BROWSER_TARGETS } = require('./browser-targets');
+
 module.exports = (api) => {
   api.cache(true);
   return {
+    // Declared here rather than left to a project .browserslistrc: without any
+    // targets preset-env compiles all the way down to ES5, regenerator and all.
+    targets: BROWSER_TARGETS,
     presets: [
-      '@babel/preset-env',
+      fromEngine('@babel/preset-env'),
       [
-        '@babel/preset-react',
+        fromEngine('@babel/preset-react'),
         {
           'runtime': 'automatic'
         }
       ],
-      '@babel/preset-typescript'
+      fromEngine('@babel/preset-typescript')
     ],
     plugins: [
       [
-        '@babel/plugin-transform-runtime',
+        fromEngine('@babel/plugin-transform-runtime'),
         {
-          'useESModules': true,
-          'regenerator': true
+          version: runtimeVersion,
+          absoluteRuntime: __dirname,
+          // babel-loader reports supportsStaticESM, so this picks helpers/esm
+          // under webpack and CJS helpers anywhere else.
+          useESModules: 'auto',
         }
       ],
       [
-        'babel-plugin-styled-components',
+        fromEngine('babel-plugin-styled-components'),
         {
           minify: true,
           transpileTemplateLiterals: true,

package/lib/browser-targets.js

@@ -0,0 +1,42 @@
+/**
+ * Single source of truth for the browser floor. Consumed by two places that
+ * would otherwise each resolve it independently:
+ *
+ *  - `babel.application.config.js` passes it to preset-env as `targets`
+ *  - `webpack-config/single-spa-defaults.js` exports it as `process.env.BROWSERSLIST`
+ *
+ * Declaring it here rather than expecting a `.browserslistrc` in every project
+ * keeps the floor from drifting per repository. Both mechanisms deliberately
+ * override any project-level browserslist config: an explicit `targets` beats a
+ * config file in babel, and the BROWSERSLIST variable short-circuits config
+ * lookup in browserslist itself.
+ *
+ * This is an honest ES2022 baseline — these are exactly the versions where the
+ * last ES2022 feature (class static initialization blocks) landed. Keep it in
+ * sync with `target`/`lib` in `lib/tsconfig.json`: library packages are emitted
+ * at that target and are never re-transpiled, because babel-loader excludes
+ * node_modules.
+ *
+ * Constraints if you ever move this floor:
+ *  - preset-env runs without useBuiltIns/core-js, so new builtins go out
+ *    unpolyfilled regardless of what is declared here. Do not drop below
+ *    Safari 15.4 — dependencies ship Object.hasOwn.
+ *  - Below Safari/iOS 16.3 preset-env turns on transform-parameters (default
+ *    and rest params rewritten to `arguments` in every function) plus the
+ *    static-block transform: roughly +5.8 KB raw / +0.9 KB gzip.
+ *  - Below Chrome/Edge 91 it enables
+ *    plugin-bugfix-v8-spread-parameters-in-optional-chaining, which downlevels
+ *    every `?.` in the bundle.
+ */
+const BROWSER_TARGETS = [
+  'Chrome >= 94',
+  'Edge >= 94',
+  'Firefox >= 93',
+  'Safari >= 16.4',
+  'iOS >= 16.4',
+];
+
+module.exports = {
+  BROWSER_TARGETS,
+  BROWSERSLIST_QUERY: BROWSER_TARGETS.join(', '),
+};

package/lib/build-babel.js

@@ -8,6 +8,13 @@ async function buildStyledComponents(
   targetDir,
 ) {
   const files = await listFilesInDirectoryRecursively(sourceDir);
+  // Only styled-components runs here. `?.` is deliberately left alone: tsc
+  // already emits it untouched at the ES2022 target, and every browser in
+  // lib/browser-targets.js supports it natively. The optional-chaining
+  // transform this used to carry was a leftover from when it was a proposal —
+  // it also depended on @babel/plugin-transform-optional-chaining resolving
+  // transitively through preset-env's tree, since it was never a declared
+  // dependency of this package.
   const options = {
     babelrc: false,
     configFile: false,
@@ -20,7 +27,6 @@ async function buildStyledComponents(
           transpileTemplateLiterals: true,
         },
       ],
-      require.resolve('@babel/plugin-transform-optional-chaining'),
     ],
   };
   const jsFiles = files.filter((file) => file.endsWith('.js'));

package/lib/tsconfig.json

@@ -1,10 +1,15 @@
 {
   "compilerOptions": {
     /* ----- Base Options ----- */
+    /* Keep `lib` pinned to `target`: preset-env runs without useBuiltIns/core-js,
+       so anything newer than ES2022 that the checker allows ships unpolyfilled.
+       Must stay in sync with the browser floor in lib/browser-targets.js, which
+       is where the engine declares it — consuming projects need no
+       .browserslistrc of their own. */
     "target": "ES2022",
     "module": "ESNext",
     "lib": [
-      "ESNext",
+      "ES2022",
       "DOM"
     ],
     "outDir": "./dist",

package/lib/webpack-config/single-spa-defaults.js

@@ -3,6 +3,16 @@ const { BundleAnalyzerPlugin } = require('webpack-bundle-analyzer');
 const ForkTsCheckerWebpackPlugin = require('fork-ts-checker-webpack-plugin');
 const SystemJSPublicPathPlugin = require('systemjs-webpack-interop/SystemJSPublicPathWebpackPlugin');
 
+const { BROWSERSLIST_QUERY } = require('../browser-targets');
+
+// browserslist reads this before it looks for any config file (see loadConfig
+// in browserslist/node.js), so it makes the engine authoritative even when a
+// project still carries a stray .browserslistrc. Passing the query inline as
+// `target: 'browserslist:<query>'` does NOT achieve this: webpack's handler
+// only falls back to treating the string as a query when no project config was
+// found at all, so a project file would silently win.
+process.env.BROWSERSLIST = BROWSERSLIST_QUERY;
+
 /**
  * Single-spa webpack configuration for React + TypeScript applications.
  * Replaces webpack-config-single-spa-react-ts package.
@@ -63,6 +73,10 @@ function singleSpaDefaults(opts) {
 
   return {
     mode: isProduction ? 'production' : 'development',
+    // Without this webpack falls back to 'web' when no browserslist config is
+    // visible — a second, drifting source of truth for the floor. Resolves
+    // against the BROWSERSLIST value set above.
+    target: 'browserslist',
     entry: path.resolve(
       process.cwd(),
       `src/${opts.orgName}-${opts.projectName}.tsx`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pushwoosh/frontend-builder-engine",
-  "version": "3.0.1",
+  "version": "3.1.0",
   "description": "Pushwoosh frontend builder engine",
   "main": "./lib/pushwoosh-frontend-builder-engine.js",
   "publishConfig": {
@@ -25,6 +25,7 @@
     "@babel/preset-env": "^7.24.3",
     "@babel/preset-react": "^7.24.1",
     "@babel/preset-typescript": "^7.24.1",
+    "@babel/runtime": "^7.29.7",
     "@babel/types": "^7.24.0",
     "@eslint/js": "^9.13.0",
     "@stylistic/eslint-plugin": "^5.3.1",