@layerzerolabs/typescript-configuration 0.2.98 → 0.2.99

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@layerzerolabs/typescript-configuration",
-  "version": "0.2.98",
+  "version": "0.2.99",
   "private": false,
   "license": "MIT",
   "devDependencies": {

package/tsconfig.base.json

@@ -10,8 +10,8 @@
         "checkJs": false,
 
         // Module Configuration
-        "module": "CommonJS",
-        "moduleResolution": "Node",
+        "module": "ESNext",
+        "moduleResolution": "bundler",
 
         // Source Map and Declaration Settings
         "sourceMap": true,

package/tsconfig.bundler.json

@@ -1,30 +0,0 @@
-{
-    "$schema": "https://json.schemastore.org/tsconfig",
-    "display": "Bundler",
-    /**
-     * Use this configuration for:
-     * - Packages that use bundlers (tsup, webpack, etc.)
-     * - Libraries that will be bundled before being consumed
-     *
-     * Note on module resolution:
-     * The bundler/ESNext configuration provides better compatibility with
-     * both ESM and CommonJS modules. Modern bundlers can handle both
-     * formats efficiently, making this the ideal choice for packages
-     * that will be bundled.
-     *
-     * Common indicators:
-     * - Presence of tsup.config.ts
-     * - Package is a shared library
-     *
-     * Do NOT use this for:
-     * - Direct Node.js applications without bundling
-     * - Scripts that run directly with node
-     * Use tsconfig.node.json instead for those cases
-     */
-    "extends": "./tsconfig.node.json",
-    "compilerOptions": {
-        // Modern bundler settings
-        "module": "ESNext",
-        "moduleResolution": "bundler"
-    }
-}

package/tsconfig.node.json

@@ -1,30 +0,0 @@
-{
-    "$schema": "https://json.schemastore.org/tsconfig",
-    "display": "Node",
-    /**
-     * Use this configuration for:
-     * - Direct Node.js applications and scripts
-     * - Server applications that run with node directly
-     * - CLI tools and scripts that aren't bundled
-     *
-     * Note on module resolution:
-     * We use NodeNext because it follows Node.js's native
-     * module resolution rules, which is ideal for applications
-     * that run directly with node without bundling.
-     *
-     * If your package uses a bundler (e.g., has tsup.config.ts),
-     * use tsconfig.bundler.json instead.
-     */
-    "extends": "./tsconfig.base.json",
-    "compilerOptions": {
-        // Node-specific module settings
-        "module": "NodeNext",
-        "moduleResolution": "NodeNext",
-
-        // Node.js Environment
-        "types": ["node"],
-
-        // Output Configuration
-        "removeComments": true
-    }
-}