@choiceform/shared-auth 0.1.1 → 0.1.2

package/LICENSE.md

@@ -0,0 +1,149 @@
+# License
+
+Portions of this software are licensed as follows:
+
+- Content of branches other than the main branch are not licensed.
+- Source code files that contain `.ee.` in their filename or `.ee` in their directory name are NOT licensed under the Sustainable Use License. To use source code files that contain `.ee.` in their filename or `.ee` in their directory name you must hold a valid Rungraf Enterprise License specifically allowing you access to such source code files and as defined in "LICENSE_EE.md".
+- All third party components incorporated into the Rungraf software are licensed under the original license provided by the owner of the applicable component.
+- Content outside of the above mentioned files or restrictions is available under the "Sustainable Use License" as defined below.
+
+---
+
+## Sustainable Use License
+
+**Version 1.0**
+
+### Acceptance
+
+By using the software, you agree to all of the terms and conditions below.
+
+### Copyright License
+
+The licensor grants you a non-exclusive, royalty-free, worldwide, non-sublicensable, non-transferable license to use, copy, distribute, make available, and prepare derivative works of the software, in each case subject to the limitations below.
+
+### Limitations
+
+You may use or modify the software only for your own internal business purposes or for non-commercial or personal use. You may distribute the software or provide it to others only if you do so free of charge for non-commercial purposes. You may not alter, remove, or obscure any licensing, copyright, or other notices of the licensor in the software. Any use of the licensor's trademarks is subject to applicable law.
+
+### Patents
+
+The licensor grants you a license, under any patent claims the licensor can license, or becomes able to license, to make, have made, use, sell, offer for sale, import and have imported the software, in each case subject to the limitations and conditions in this license. This license does not cover any patent claims that you cause to be infringed by modifications or additions to the software. If you or your company make any written claim that the software infringes or contributes to infringement of any patent, your patent license for the software granted under these terms ends immediately. If your company makes such a claim, your patent license ends immediately for work on behalf of your company.
+
+### Notices
+
+You must ensure that anyone who gets a copy of any part of the software from you also gets a copy of these terms. If you modify the software, you must include in any modified copies of the software a prominent notice stating that you have modified the software.
+
+### No Other Rights
+
+These terms do not imply any licenses other than those expressly granted in these terms.
+
+### Termination
+
+If you use the software in violation of these terms, such use is not licensed, and your license will automatically terminate. If the licensor provides you with a notice of your violation, and you cease all violation of this license no later than 30 days after you receive that notice, your license will be reinstated retroactively. However, if you violate these terms after such reinstatement, any additional violation of these terms will cause your license to terminate automatically and permanently.
+
+### No Liability
+
+As far as the law allows, the software comes as is, without any warranty or condition, and the licensor will not be liable to you for any damages arising out of these terms or the use or nature of the software, under any kind of legal claim.
+
+### Definitions
+
+- The **"licensor"** is the entity offering these terms, which is the Rungraf project and its contributors.
+
+- The **"software"** is the software the licensor makes available under these terms, including any portion of it.
+
+- **"You"** refers to the individual or entity agreeing to these terms.
+
+- **"Your company"** is any legal entity, sole proprietorship, or other kind of organization that you work for, plus all organizations that have control over, are under the control of, or are under common control with that organization. Control means ownership of substantially all the assets of an entity, or the power to direct its management and policies by vote, contract, or otherwise. Control can be direct or indirect.
+
+- **"Your license"** is the license granted to you for the software under these terms.
+
+- **"Use"** means anything you do with the software requiring your license.
+
+- **"Trademark"** means trademarks, service marks, and similar rights.
+
+---
+
+## Additional Terms for Rungraf
+
+In addition to the Sustainable Use License terms above, the following specific limitations apply to Rungraf:
+
+### Multi-Tenant SaaS Restriction
+
+You may NOT use Rungraf to operate a multi-tenant Software-as-a-Service (SaaS) offering where you provide Rungraf as a hosted service to multiple external customers or organizations, unless you obtain a separate commercial license from the Rungraf project.
+
+**Examples of PROHIBITED use without commercial license:**
+- Operating "AI Agent Platform as a Service" for multiple paying customers
+- Providing Rungraf as a white-labeled workflow automation service
+- Running a marketplace where multiple organizations build AI Agents on your hosted Rungraf instance
+
+**Examples of PERMITTED use:**
+- Deploying Rungraf within your organization for your employees and internal use
+- Embedding Rungraf in your product where each customer gets their own dedicated Rungraf instance
+- Using Rungraf as a backend service for your own application (single-tenant)
+
+**Workspace Definition:** Within Rungraf, one workspace represents one tenant. A workspace provides an isolated environment for each tenant's AI Agents, workflows, data, and configurations.
+
+### Branding and Attribution
+
+When using Rungraf's frontend interface, you may not remove, alter, or obscure the Rungraf logo, branding, or copyright notices displayed in the user interface. This restriction applies only to the visual frontend components.
+
+**Frontend Definition:** The "frontend" of Rungraf includes all components located in the `packages/client/` directory when running from source code, or the "client" Docker image when running via containers.
+
+**Examples of PERMITTED use:**
+- Using only Rungraf's backend APIs with your own custom frontend (no branding requirement)
+- Forking and customizing the codebase while maintaining attribution
+- White-labeling with a separate commercial license
+
+**Examples of PROHIBITED use:**
+- Using the Rungraf frontend with logos and branding removed
+- Distributing modified versions without proper attribution
+
+### Core Engine Protection
+
+The Rungraf AI Agent Runtime (located in `packages/runner/`) and Expression Engine may be used and modified for your own purposes, but you may NOT:
+
+- Extract the Agent Runtime as a standalone product and sell it separately
+- Use Rungraf's core orchestration engine to build a competing workflow automation platform for sale
+- Offer the Expression Engine as a standalone commercial service
+
+**Examples of PERMITTED use:**
+- Integrating Rungraf into your product's backend
+- Modifying the runtime for your specific use case
+- Contributing improvements back to the open source project
+
+**Examples of PROHIBITED use:**
+- Packaging the Elixir Agent Runtime as "SuperAgent Engine" and selling it
+- Building a competitor workflow platform using Rungraf's core code
+
+---
+
+## Fair Code Principles
+
+Rungraf follows the [Fair Code](https://faircode.io) principles. We believe in:
+
+1. **Transparency**: Source code is publicly available for review and contribution
+2. **Sustainability**: Protecting the project's ability to fund ongoing development
+3. **Community**: Encouraging contributions while preventing exploitation
+4. **Freedom**: Allowing use for internal business purposes and non-commercial projects
+
+---
+
+## Getting a Commercial License
+
+If your use case falls under the restrictions above, you can obtain a commercial Rungraf Enterprise License. Enterprise licenses include:
+
+- Multi-tenant SaaS deployment rights
+- White-labeling permissions
+- Priority support and SLA guarantees
+- Enterprise features (SSO, advanced RBAC, audit logs)
+- Custom development support
+
+Contact us for enterprise licensing:
+- **Email**: [enterprise@rungraf.io](mailto:enterprise@rungraf.io)
+- **Website**: [https://rungraf.io/enterprise](https://rungraf.io/enterprise)
+
+---
+
+**© 2024-2025 Rungraf Project**
+
+This software is provided "as is", without warranty of any kind, express or implied.

package/README.md

@@ -14,6 +14,7 @@
 - ✅ 预配置的 API 客户端（自动添加认证头）
 - ✅ 用户管理器工具
 - ✅ 响应式状态管理（基于 Legend State）
+- ✅ 自动伴生团队设置（登录时自动获取并设置活动组织和团队）
 
 ## 安装
 
@@ -32,6 +33,15 @@ VITE_AUTH_API_URL=http://localhost:4320
 
 **注意：** 如果你的项目仍在使用 `VITE_CORE_AI_API_URL`，代码会自动向后兼容，但建议迁移到新的 `VITE_AUTH_API_URL`。
 
+### 伴生团队功能
+
+`AuthSync` 组件会在用户登录成功后自动：
+1. 从 OneAuth API 获取用户的组织信息
+2. 设置活动组织
+3. 设置活动团队（如果存在）
+
+此功能需要 `VITE_AUTH_API_URL` 环境变量已配置。如果未配置，功能会静默跳过，不影响登录流程。
+
 ## 快速开始
 
 ### 1. 初始化认证系统
@@ -155,6 +165,21 @@ function LoginPage() {
 - `apiClient`: 预配置的 API 客户端（包含 get/post/put/delete 方法）
 - `userManager`: 用户管理器（包含 getUser/getUserId 方法）
 
+### `AuthSync`
+
+Better Auth 认证状态同步组件。
+
+**功能：**
+- 同步 better-auth 的 session 状态到应用 store
+- 在用户登录成功后自动设置伴生团队（活动组织和团队）
+- 使用响应式状态监听，确保状态同步的实时性
+
+**Props：**
+
+- `auth`: AuthInstance
+
+**注意：** 此组件需要在应用的根组件中渲染，通常与 `ProtectedRoute` 一起使用。
+
 ### `ProtectedRoute`
 
 路由保护组件。
@@ -447,6 +472,32 @@ A: `apiClient` 会自动处理 401 响应，当检测到未授权时会调用 `h
 
 A: 可以使用 `createAuth` 替代 `initAuth`，它提供更多配置选项，包括自定义回调 URL 构建函数等。
 
+### Q: 伴生团队功能是什么？
+
+A: 在用户登录成功后，`AuthSync` 组件会自动：
+- 从 OneAuth API (`/v1/organizations/me`) 获取用户的组织信息
+- 调用 better-auth API 设置活动组织 (`/v1/auth/organization/set-active`)
+- 调用 better-auth API 设置活动团队 (`/v1/auth/organization/set-active-team`)
+
+这确保了用户在登录后拥有正确的权限上下文。如果此功能失败，不会影响登录流程，只会在控制台记录错误信息。
+
+### Q: 如何禁用伴生团队功能？
+
+A: 不配置 `VITE_AUTH_API_URL` 环境变量即可。功能会静默跳过。
+
+## 更新日志
+
+### v0.1.2
+
+- ✨ 新增：登录时自动获取并设置伴生团队功能
+- 🔧 改进：优化错误处理和边缘情况处理
+- 📝 改进：完善代码文档和注释
+- 🐛 修复：修复 token 编码问题，确保 API 调用正常工作
+
+### v0.1.1
+
+- 初始版本
+
 ## 许可证
 
 MIT

package/dist/components/auth-sync.d.ts

@@ -1,7 +1,22 @@
 import type { AuthInstance } from "../core";
 /**
  * Better Auth 认证状态同步组件
- * 使用官方的 useSession hook 同步认证状态
+ *
+ * 功能说明：
+ * - 使用 better-auth 的 useSession hook 同步认证状态到应用 store
+ * - 监听 authStore 状态，在用户登录成功后自动设置伴生团队
+ * - 确保登录流程的完整性和权限上下文的正确性
+ *
+ * 技术实现：
+ * - 使用 Legend State 的 use$ hook 响应式监听状态变化
+ * - 使用 useRef 确保伴生团队设置只执行一次
+ * - 分离 session 同步和团队设置的逻辑，保持代码清晰
+ *
+ * 边缘情况处理：
+ * - Session 加载中：设置 loading 状态
+ * - Session 错误：清空用户信息，重置团队设置状态
+ * - 无 Session 但有用户：保持用户信息（可能从 token 加载）
+ * - 用户登出：重置团队设置状态，允许下次登录时重新设置
  */
 export declare function AuthSync({ auth }: {
     auth: AuthInstance;

package/dist/components/auth-sync.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"auth-sync.d.ts","sourceRoot":"","sources":["../../src/components/auth-sync.tsx"],"names":[],"mappings":"AACA,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,SAAS,CAAA;AA8C3C;;;GAGG;AACH,wBAAgB,QAAQ,CAAC,EAAE,IAAI,EAAE,EAAE;IAAE,IAAI,EAAE,YAAY,CAAA;CAAE,QA8BxD"}
+{"version":3,"file":"auth-sync.d.ts","sourceRoot":"","sources":["../../src/components/auth-sync.tsx"],"names":[],"mappings":"AAEA,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,SAAS,CAAA;AAwP3C;;;;;;;;;;;;;;;;;;GAkBG;AACH,wBAAgB,QAAQ,CAAC,EAAE,IAAI,EAAE,EAAE;IAAE,IAAI,EAAE,YAAY,CAAA;CAAE,QAoFxD"}

package/dist/components/auth-sync.js

@@ -1,4 +1,5 @@
-import { useEffect } from "react";
+import { useEffect, useRef } from "react";
+import { use$ } from "@legendapp/state/react";
 /**
  * 将日期转换为 ISO 字符串
  */
@@ -26,35 +27,278 @@ function mapSessionUserToSessionUser(sessionUser, sessionCreatedAt) {
         updatedAt: toISOString(sessionUser.updatedAt) ?? "",
     };
 }
+/**
+ * 检查是否为开发环境
+ */
+const isDev = import.meta.env?.DEV ?? false;
+/**
+ * 安全获取环境变量
+ */
+function getEnvVar(key) {
+    return import.meta.env?.[key];
+}
+/**
+ * 解析 API 错误响应
+ */
+async function parseErrorResponse(response) {
+    try {
+        const text = await response.text();
+        if (text) {
+            try {
+                const json = JSON.parse(text);
+                if (typeof json === "object" && json !== null) {
+                    const data = json;
+                    if (typeof data.error === "object" && data.error !== null) {
+                        const errorObj = data.error;
+                        if (typeof errorObj.message === "string") {
+                            return errorObj.message;
+                        }
+                    }
+                    else if (typeof data.message === "string") {
+                        return data.message;
+                    }
+                }
+            }
+            catch {
+                // 如果不是 JSON，返回原始文本（限制长度）
+                return text.length < 200 ? text : `${text.substring(0, 200)}...`;
+            }
+        }
+    }
+    catch {
+        // 忽略解析错误
+    }
+    return `HTTP ${response.status}: ${response.statusText}`;
+}
+/**
+ * 获取或创建伴生团队
+ *
+ * 功能说明：
+ * - 在用户登录成功后自动获取组织信息
+ * - 设置活动组织和团队，确保用户拥有正确的权限上下文
+ * - 使用 fetch API 直接调用 oneauth 和 better-auth 的 API
+ * - 所有错误都会被捕获，不会影响登录流程
+ *
+ * 边缘情况处理：
+ * - 环境变量未配置：静默跳过
+ * - Token 缺失：静默跳过
+ * - 网络错误：记录错误但不抛出
+ * - API 返回错误：记录详细错误信息
+ * - 无效响应数据：记录错误但不影响登录
+ */
+async function setupCompanionTeam(_auth, token) {
+    try {
+        // 1. 验证环境变量配置
+        const oneAuthBaseUrl = getEnvVar("VITE_AUTH_API_URL") || getEnvVar("VITE_CORE_AI_API_URL");
+        if (!oneAuthBaseUrl) {
+            if (isDev) {
+                console.warn("[AuthSync] VITE_AUTH_API_URL is not configured, skipping companion team setup");
+            }
+            return;
+        }
+        // 2. 验证 token
+        if (!token || typeof token !== "string" || token.trim().length === 0) {
+            if (isDev) {
+                console.warn("[AuthSync] Token is missing or invalid, skipping companion team setup");
+            }
+            return;
+        }
+        // 3. 获取 token（优先使用 oneauth_token，如果没有则使用传入的 token）
+        const oneAuthTokenFromStorage = localStorage.getItem("oneauth_token");
+        const oneAuthToken = oneAuthTokenFromStorage ?? token;
+        if (!oneAuthToken || oneAuthToken.trim().length === 0) {
+            if (isDev) {
+                console.warn("[AuthSync] No valid token available, skipping companion team setup");
+            }
+            return;
+        }
+        // 4. Token 编码（与 fetchSessionWithToken 保持一致）
+        const encodedToken = encodeURIComponent(oneAuthToken);
+        // 5. 获取组织信息
+        const myOrganizationUrl = `${oneAuthBaseUrl}/v1/organizations/me`;
+        if (isDev) {
+            console.log("[AuthSync] Fetching organization from:", myOrganizationUrl);
+        }
+        const orgResponse = await fetch(myOrganizationUrl, {
+            headers: {
+                Authorization: `Bearer ${encodedToken}`,
+                "Content-Type": "application/json",
+            },
+        });
+        if (!orgResponse.ok) {
+            const errorMessage = await parseErrorResponse(orgResponse);
+            throw new Error(`Failed to fetch organization: ${errorMessage}`);
+        }
+        // 6. 解析组织数据
+        let orgResponseData;
+        try {
+            orgResponseData = await orgResponse.json();
+        }
+        catch (parseError) {
+            throw new Error(`Failed to parse organization response: ${parseError instanceof Error ? parseError.message : String(parseError)}`);
+        }
+        // 7. 提取组织对象（支持 {data: {...}} 或直接是组织对象）
+        const organization = orgResponseData?.data ||
+            orgResponseData;
+        // 8. 验证组织数据
+        if (!organization || typeof organization !== "object" || !organization.id || typeof organization.id !== "string") {
+            throw new Error(`Invalid organization data received: missing or invalid organization ID`);
+        }
+        // 9. 获取 auth baseURL
+        const authBaseURL = getEnvVar("VITE_AUTH_API_URL") ||
+            getEnvVar("VITE_CORE_AI_API_URL") ||
+            "http://localhost:4320";
+        // 10. 设置活动组织
+        const setActiveOrgUrl = `${authBaseURL}/v1/auth/organization/set-active`;
+        if (isDev) {
+            console.log("[AuthSync] Setting active organization:", { organizationId: organization.id });
+        }
+        const setActiveOrgResponse = await fetch(setActiveOrgUrl, {
+            method: "POST",
+            headers: {
+                Authorization: `Bearer ${encodedToken}`,
+                "Content-Type": "application/json",
+            },
+            body: JSON.stringify({ organizationId: organization.id }),
+        });
+        if (!setActiveOrgResponse.ok) {
+            const errorMessage = await parseErrorResponse(setActiveOrgResponse);
+            throw new Error(`Failed to set active organization: ${errorMessage}`);
+        }
+        // 11. 设置活动团队（如果有团队）
+        if (organization.teams && Array.isArray(organization.teams) && organization.teams.length > 0) {
+            const firstTeam = organization.teams[0];
+            if (firstTeam && firstTeam.id && typeof firstTeam.id === "string") {
+                const setActiveTeamUrl = `${authBaseURL}/v1/auth/organization/set-active-team`;
+                if (isDev) {
+                    console.log("[AuthSync] Setting active team:", { teamId: firstTeam.id });
+                }
+                const setActiveTeamResponse = await fetch(setActiveTeamUrl, {
+                    method: "POST",
+                    headers: {
+                        Authorization: `Bearer ${encodedToken}`,
+                        "Content-Type": "application/json",
+                    },
+                    body: JSON.stringify({ teamId: firstTeam.id }),
+                });
+                if (!setActiveTeamResponse.ok) {
+                    const errorMessage = await parseErrorResponse(setActiveTeamResponse);
+                    throw new Error(`Failed to set active team: ${errorMessage}`);
+                }
+                if (isDev) {
+                    console.log("[AuthSync] Successfully set active team");
+                }
+            }
+            else if (isDev) {
+                console.warn("[AuthSync] First team has invalid ID, skipping team setup");
+            }
+        }
+        else if (isDev) {
+            console.log("[AuthSync] No teams found in organization");
+        }
+    }
+    catch (error) {
+        // 记录错误但不抛出，避免影响登录流程
+        const errorMessage = error instanceof Error ? error.message : String(error);
+        console.error("[AuthSync] Failed to setup companion team:", errorMessage);
+        // 在开发环境下输出更详细的错误信息
+        if (isDev && error instanceof Error) {
+            console.error("[AuthSync] Error details:", {
+                message: error.message,
+                stack: error.stack,
+            });
+        }
+    }
+}
 /**
  * Better Auth 认证状态同步组件
- * 使用官方的 useSession hook 同步认证状态
+ *
+ * 功能说明：
+ * - 使用 better-auth 的 useSession hook 同步认证状态到应用 store
+ * - 监听 authStore 状态，在用户登录成功后自动设置伴生团队
+ * - 确保登录流程的完整性和权限上下文的正确性
+ *
+ * 技术实现：
+ * - 使用 Legend State 的 use$ hook 响应式监听状态变化
+ * - 使用 useRef 确保伴生团队设置只执行一次
+ * - 分离 session 同步和团队设置的逻辑，保持代码清晰
+ *
+ * 边缘情况处理：
+ * - Session 加载中：设置 loading 状态
+ * - Session 错误：清空用户信息，重置团队设置状态
+ * - 无 Session 但有用户：保持用户信息（可能从 token 加载）
+ * - 用户登出：重置团队设置状态，允许下次登录时重新设置
  */
 export function AuthSync({ auth }) {
-    const { authClient, authActions } = auth;
-    const { data: session, isPending, error } = authClient.useSession();
+    const { authClient, authActions, tokenStorage, authStore } = auth;
+    // 监听 authStore 中的用户状态（响应式）
+    const user = use$(authStore.user);
+    const isAuthenticated = use$(authStore.isAuthenticated);
+    const isLoaded = use$(authStore.isLoaded);
+    // 监听 better-auth 的 session（用于同步到 store）
+    const sessionResult = authClient.useSession();
+    const { data: session, isPending, error } = sessionResult || {
+        data: null,
+        isPending: false,
+        error: null
+    };
+    // 使用 ref 确保伴生团队设置只执行一次
+    const teamSetupRef = useRef(false);
+    // Effect 1: 同步 better-auth session 到 store
     useEffect(() => {
-        // 根据 session 状态更新 store
+        // 加载中状态
         if (isPending) {
             authActions.setLoading(true);
+            return;
         }
-        else {
-            authActions.setLoading(false);
-            if (error) {
-                authActions.setError(error.message || "Authentication error");
-                authActions.initialize(null, true);
-            }
-            else if (session) {
-                // 映射用户数据：使用 session 的创建时间作为最后登录时间
-                const user = mapSessionUserToSessionUser(session.user, session.session?.createdAt);
-                authActions.initialize(user, true);
+        authActions.setLoading(false);
+        // 错误处理
+        if (error) {
+            const errorMessage = error instanceof Error
+                ? error.message
+                : (typeof error === "string" ? error : "Authentication error");
+            authActions.setError(errorMessage);
+            authActions.initialize(null, true);
+            teamSetupRef.current = false;
+            return;
+        }
+        // Session 存在：映射用户数据并更新 store
+        if (session?.user) {
+            try {
+                const mappedUser = mapSessionUserToSessionUser(session.user, session.session?.createdAt);
+                authActions.initialize(mappedUser, true);
             }
-            else {
-                // 没有 session，清空用户信息
-                authActions.initialize(null, true);
+            catch (mappingError) {
+                console.error("[AuthSync] Failed to map session user:", mappingError);
+                // 映射失败时不清空用户信息，可能已有有效的用户数据
             }
         }
+        // 注意：没有 session 时不主动清空用户信息，因为可能已经从 token 加载了
     }, [session, isPending, error, authActions]);
+    // Effect 2: 监听 authStore 状态，设置伴生团队
+    useEffect(() => {
+        // 条件检查：只有在用户已认证且已加载完成时才设置伴生团队
+        if (isLoaded && isAuthenticated && user?.id && !teamSetupRef.current) {
+            teamSetupRef.current = true;
+            const token = tokenStorage.get();
+            // 验证 token 存在
+            if (token && typeof token === "string" && token.trim().length > 0) {
+                setupCompanionTeam(auth, token).catch((error) => {
+                    const errorMessage = error instanceof Error ? error.message : String(error);
+                    console.error("[AuthSync] Failed to setup companion team:", errorMessage);
+                    // 失败后重置 ref，允许在特定条件下重试（如 token 更新后）
+                    teamSetupRef.current = false;
+                });
+            }
+            else if (isDev) {
+                console.warn("[AuthSync] Token not found or invalid, cannot setup companion team");
+            }
+        }
+        // 用户登出：重置 ref，允许下次登录时重新设置
+        if (isLoaded && !isAuthenticated) {
+            teamSetupRef.current = false;
+        }
+    }, [user, isAuthenticated, isLoaded, auth, tokenStorage]);
     // 这是一个隐形组件，不渲染任何内容
     return null;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@choiceform/shared-auth",
-  "version": "0.1.1",
+  "version": "0.1.2",
   "description": "Shared authentication package for Choiceform projects",
   "type": "module",
   "main": "./dist/index.js",
@@ -16,12 +16,6 @@
     "dist",
     "README.md"
   ],
-  "scripts": {
-    "build": "tsc",
-    "dev": "tsc --watch",
-    "clean": "rimraf dist",
-    "prepublishOnly": "pnpm run build"
-  },
   "repository": {
     "type": "git",
     "url": "git+https://github.com/choiceform/automation.git",
@@ -57,6 +51,10 @@
     "@types/react-dom": "18.2.22",
     "typescript": "^5.5.3",
     "rimraf": "^6.0.1"
+  },
+  "scripts": {
+    "build": "tsc",
+    "dev": "tsc --watch",
+    "clean": "rimraf dist"
   }
-}
-
+}