nitrostack 1.0.5 → 1.0.7

package/CHANGELOG.md

@@ -8,6 +8,33 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.0.7] - 2025-10-27
+
+### Fixed
+- **Critical**: Fixed webpack loader configuration error for Studio
+  - Switched from manual `next-swc-loader` configuration to Next.js's `defaultLoaders.babel`
+  - Resolves "TypeError [ERR_INVALID_ARG_TYPE]: The 'from' argument must be of type string" error
+  - Uses Next.js's pre-configured loader with all correct options
+
+### Technical Details
+- Previous manual loader configuration was passing incorrect options to `next-swc-loader`
+- New approach: use `defaultLoaders.babel` provided by Next.js webpack context
+- This ensures all TypeScript/JSX files in `lib/` and `components/` are processed with the correct Babel/SWC configuration
+
+## [1.0.6] - 2025-10-27
+
+### Fixed
+- **Critical**: Added explicit webpack rule for Studio TypeScript compilation
+  - Created dedicated webpack rule with `next-swc-loader` for `lib/` and `components/` directories
+  - Uses `include` directive to explicitly process TypeScript files in these directories
+  - Resolves "Module parse failed: Unexpected token" by ensuring proper TypeScript compilation
+  - Works correctly when Studio is installed from npm in `node_modules`
+
+### Technical Details
+- Previous approach of modifying `exclude` patterns wasn't working consistently
+- New approach: explicitly `push` a new webpack rule that includes our directories
+- Uses Next.js's internal `next-swc-loader` with proper configuration for both client and server builds
+
 ## [1.0.5] - 2025-10-27
 
 ### Fixed

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "nitrostack",
-  "version": "1.0.5",
+  "version": "1.0.7",
   "description": "NitroStack - Build powerful MCP servers with TypeScript",
   "type": "module",
   "main": "dist/core/index.js",

package/src/studio/next.config.js

@@ -16,37 +16,23 @@ const nextConfig = {
   eslint: {
     ignoreDuringBuilds: true,
   },
-  webpack: (config) => {
+  webpack: (config, { defaultLoaders, isServer }) => {
     // Explicitly configure webpack to resolve @ alias
     config.resolve.alias = {
       ...config.resolve.alias,
       '@': __dirname,
     };
 
-    // Ensure TypeScript files are processed correctly
-    // Remove exclude patterns that might block our lib/components from being processed
-    config.module.rules.forEach((rule) => {
-      if (rule.test && rule.test.toString().includes('tsx')) {
-        // Remove node_modules exclude or modify it to allow our files
-        if (rule.exclude) {
-          const originalExclude = rule.exclude;
-          rule.exclude = (modulePath) => {
-            // Allow our lib and components directories
-            if (modulePath.includes(path.join(__dirname, 'lib')) || 
-                modulePath.includes(path.join(__dirname, 'components'))) {
-              return false;
-            }
-            // Apply original exclude logic
-            if (typeof originalExclude === 'function') {
-              return originalExclude(modulePath);
-            }
-            if (originalExclude instanceof RegExp) {
-              return originalExclude.test(modulePath);
-            }
-            return false;
-          };
-        }
-      }
+    // Ensure our lib and components directories are included in compilation
+    // Use Next.js's default TypeScript loader
+    const libPath = path.resolve(__dirname, 'lib');
+    const componentsPath = path.resolve(__dirname, 'components');
+
+    // Add a rule for our TypeScript files using Next.js's default loader
+    config.module.rules.push({
+      test: /\.(ts|tsx)$/,
+      include: [libPath, componentsPath],
+      use: defaultLoaders.babel,
     });
 
     return config;