nucleus-core-ts 0.9.758 → 0.9.759

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "nucleus-core-ts",
-	"version": "0.9.758",
+	"version": "0.9.759",
 	"description": "Production-ready, enterprise-grade TypeScript framework for building multi-tenant APIs",
 	"author": "Hidayet Can Özcan <hidayetcan@gmail.com>",
 	"license": "SEE LICENSE IN LICENSE",

package/scripts/generate-schema.ts

@@ -545,8 +545,29 @@ function main() {
   }
 
   const enabledFeatures = getEnabledFeatures(config)
-  const enabledSystemTables = systemTables.tables.filter((t) => isTableEnabled(t, enabledFeatures))
   const customTables = config.entities || []
+
+  // A consumer's own entity WINS over a same-named system table.
+  //
+  // Without this, switching a feature on emits a second `export const <name>`
+  // for a table the app already declares, and the generated schema.ts no longer
+  // parses — the app crash-loops on boot with "already been declared", far from
+  // the config change that caused it. The app's own definition is the one its
+  // code and data depend on, so the system copy is the one to drop.
+  const customTableNames = new Set(customTables.map((t) => t.table_name))
+  const enabledSystemTables = systemTables.tables
+    .filter((t) => isTableEnabled(t, enabledFeatures))
+    .filter((t) => {
+      if (!customTableNames.has(t.table_name)) return true
+      console.warn(
+        `[Schema] "${t.table_name}" is declared in config.entities AND ships as a system table ` +
+          `(feature: ${t.feature_set?.join(', ') || 'none'}). Using YOUR definition and skipping ` +
+          `the built-in one. Nucleus features that read this table expect the built-in columns — ` +
+          `rename your entity if you want both.`
+      )
+      return false
+    })
+
   const allTables = [...enabledSystemTables, ...customTables]
 
   if (!fs.existsSync(outputDir)) {