cdeops 13.1.2-alpha.9 → 13.1.3-alpha.2

package/client.mjs

@@ -0,0 +1,13 @@
+// This is the module that is bundled with extensions when they use `import ... from 'cdeops/client'`.
+// It delegates to the extension host's runtime implementation of this module by calling
+// `globalThis.require` (which ensures that the extension host's `require` is called at runtime).
+//
+// This dummy file is used when extension is bundled with a JavaScript bundler that lacks support for externals
+// (or when `cdeops/client` is not configured as an external module). Parcel does not support externals
+// (https://github.com/parcel-bundler/parcel/issues/144). Webpack, Rollup, and Microbundle support externals.
+
+// ESM named exports must be statically analyzable, so we can only reliably export the module as default.
+// Consumers should use: import cdeopsClient from 'cdeops/client'; then access cdeopsClient.commands, etc.
+// Or use: import cdeopsClient from 'cdeops/client'; const { commands, configuration } = cdeopsClient;
+const cdeopsClient = globalThis.require('cdeops/client');
+export default cdeopsClient;

package/package.json

@@ -1,18 +1,48 @@
 {
     "name": "cdeops",
-    "version": "13.1.2-alpha.9",
+    "version": "13.1.3-alpha.2",
     "description": "Cdecode - Extension API: build extensions that enhance coding experience in your cdeops editor",
     "license": "Apache-2.0",
     "author": "CDMBase LLC",
     "sideEffects": false,
-    "main": "src/index.js",
-    "module": "src/index.js",
+    "exports": {
+        ".": {
+            "types": "./src/cdeops.d.ts",
+            "import": "./src/index.mjs",
+            "require": "./src/index.js",
+            "default": "./src/index.js"
+        },
+        "./client": {
+            "types": "./client.d.ts",
+            "import": "./client.mjs",
+            "require": "./client.js",
+            "default": "./client.js"
+        },
+        "./server": {
+            "types": "./server.d.ts",
+            "browser": "./server.browser.mjs",
+            "import": "./server.browser.mjs",
+            "require": "./server.js",
+            "node": "./server.mjs",
+            "default": "./server.browser.mjs"
+        }
+    },
+    "main": "./src/index.js",
+    "module": "./src/index.mjs",
+    "browser": {
+        "./server.mjs": "./server.browser.mjs",
+        "./server.js": "./server.browser.mjs",
+        "cdeops/server": "./server.browser.mjs"
+    },
     "types": "./src/cdeops.d.ts",
     "files": [
         "server.d.ts",
         "server.js",
+        "server.mjs",
+        "server.browser.mjs",
         "client.d.ts",
         "client.js",
+        "client.mjs",
         "src",
         "dist/docs"
     ],
@@ -29,5 +59,5 @@
     "publishConfig": {
         "access": "public"
     },
-    "gitHead": "1049eb9b6d34f64db1d0e1a85a21924eda9d4ff9"
+    "gitHead": "394adad29e2a114eb360b13076eab61df7d2d14a"
 }

package/server.browser.mjs

@@ -0,0 +1,28 @@
+// ESM version of cdeops/server
+// This is the module that is bundled with extensions when they use `import ... from 'cdeops/server'`.
+// It delegates to the extension host's runtime implementation of this module by calling
+// `globalThis.require` (which ensures that the extension host's `require` is called at runtime).
+
+// For ESM environments, we need to use dynamic import or globalThis
+let serverModule;
+
+if (typeof globalThis !== 'undefined' && typeof globalThis.require === 'function') {
+    serverModule = globalThis.require('cdeops/server');
+} else {
+    // Fallback: export an empty object or stub
+    // This allows the module to be imported without errors during SSR/bundling
+    serverModule = {};
+}
+
+export default serverModule;
+
+// Re-export common server exports if they exist
+export const { 
+    createConnection,
+    Connection,
+    TextDocuments,
+    TextDocumentSyncKind,
+    InitializeParams,
+    InitializeResult,
+    ServerCapabilities,
+} = serverModule || {};

package/server.mjs

@@ -0,0 +1,13 @@
+// This is the module that is bundled with extensions when they use `import ... from 'cdeops/server'`.
+// It delegates to the extension host's runtime implementation of this module by calling
+// `globalThis.require` (which ensures that the extension host's `require` is called at runtime).
+//
+// This dummy file is used when extension is bundled with a JavaScript bundler that lacks support for externals
+// (or when `cdeops/server` is not configured as an external module). Parcel does not support externals
+// (https://github.com/parcel-bundler/parcel/issues/144). Webpack, Rollup, and Microbundle support externals.
+
+// ESM named exports must be statically analyzable, so we can only reliably export the module as default.
+// Consumers should use: import cdeopsServer from 'cdeops/server'; then access cdeopsServer.commands, etc.
+// Or use: import cdeopsServer from 'cdeops/server'; const { commands, configuration } = cdeopsServer;
+const cdeopsServer = globalThis.require('cdeops/server');
+export default cdeopsServer;

package/src/index.mjs

@@ -0,0 +1,13 @@
+// This is the module that is bundled with extensions when they use `import ... from 'cdeops'`.
+// It delegates to the extension host's runtime implementation of this module by calling
+// `globalThis.require` (which ensures that the extension host's `require` is called at runtime).
+//
+// This dummy file is used when extension is bundled with a JavaScript bundler that lacks support for externals
+// (or when `cdeops` is not configured as an external module). Parcel does not support externals
+// (https://github.com/parcel-bundler/parcel/issues/144). Webpack, Rollup, and Microbundle support externals.
+
+// ESM named exports must be statically analyzable, so we can only reliably export the module as default.
+// Consumers should use: import cdeops from 'cdeops'; then access cdeops.workspace, cdeops.commands, etc.
+// Or use: import cdeops from 'cdeops'; const { workspace, commands } = cdeops;
+const cdeops = globalThis.require('cdeops');
+export default cdeops;