@commonplaces/oxlint-plugin 0.7.0 → 0.8.0

package/README.md

@@ -1,7 +1,7 @@
 # @commonplaces/oxlint-plugin
 
 108 custom Oxlint rules for strict Effect TypeScript, Alchemy and general code
-checks. Version 0.7.0 supports **Oxlint 1.87.0, 1.88.0 or 1.89.0** and **Node 22.14 or newer**.
+checks. Version 0.8.0 supports **Oxlint 1.87.0, 1.88.0 or 1.89.0** and **Node 22.14 or newer**.
 Oxlint's JavaScript plugin API is experimental, so upgrade it only after running
 the rule tests. The development tools use 1.89.0; consuming projects may use any supported version.
 All three exact versions are checked with independently installed archives. ESLint is not a supported host.
@@ -12,14 +12,14 @@ Effect setup below after dependency installation.
 
 ## Install
 
-Install version 0.7.0 and save its exact version:
+Install version 0.8.0 and save its exact version:
 
 ```sh
-npm install --save-dev --save-exact @commonplaces/oxlint-plugin@0.7.0 \
+npm install --save-dev --save-exact @commonplaces/oxlint-plugin@0.8.0 \
   @effect/tsgo@0.55.0 oxlint@1.89.0 oxlint-tsgolint@7.0.2004 typescript@7.0.2
 ```
 
-Version 0.7.0 supports exactly Oxlint 1.87.0, 1.88.0 or 1.89.0. Older releases
+Version 0.8.0 supports exactly Oxlint 1.87.0, 1.88.0 or 1.89.0. Older releases
 keep their earlier host lists. Consumer adoption is a separate step.
 
 The manifest and lockfile retain the resolved version. Historical GitHub release
@@ -200,6 +200,15 @@ loops, mutation, unchecked access, thrown failures and unapproved runtime calls.
 The collection convention accepts `Array.reduce(initial, callback)(values)`;
 its three-argument form `Array.reduce(values, initial, callback)` still fails.
 
+`strict-effect/no-promise-workflow` also rejects every runtime `import()` expression,
+including imports wrapped in `Effect.tryPromise` and imports in exact
+`allowedFiles` or `promiseOnlyFiles` owners. Those permissions adapt host Promise
+contracts; they do not permit dynamic module loading. Use static imports and
+defer service initialisation through native Effect or Atom lifetimes where needed.
+Static imports, re-exports and TypeScript-only `import("module").Type` references
+remain valid. Framework-generated output stays subject to the consumer's existing
+generated-file exclusions; there is no adapter exception to this prohibition.
+
 ### Supported-host adjustments
 
 The imported configurations need two small adjustments; these are separate

package/dist/strict-effect.js

@@ -961,6 +961,7 @@ const noPromiseWorkflow = defineRule({
         messages: {
             forbidden: "Use Effect for asynchronous work. Only an explicitly named host adapter may mention Promise; async, await and Promise chains remain forbidden there.",
             bridge: "Use a native Effect or Alchemy operation. Promise conversion belongs only in an explicitly named host or SDK adapter.",
+            dynamicImport: "Dynamic imports are forbidden, including in host and SDK adapters. Use a static import; Effect and Atom may defer initialisation, not module loading.",
         },
     },
     create(context) {
@@ -983,6 +984,9 @@ const noPromiseWorkflow = defineRule({
             FunctionExpression: checkFunction,
             FunctionDeclaration: checkFunction,
             AwaitExpression: report,
+            ImportExpression(node) {
+                context.report({ node, messageId: "dynamicImport" });
+            },
             NewExpression(node) {
                 if (isGlobalPromise(node.callee))
                     report(node);

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@commonplaces/oxlint-plugin",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "Shared Oxlint rules for strict Effect TypeScript, Alchemy and repository code.",
   "license": "MIT",
   "author": "Cooper Corbett",