refactor: migration to turborepo monorepo

Author: MihalyToth20

.changeset/eight-states-hear.md

@@ -1,6 +1,8 @@
 ---
-"@calycode/core": patch
-"@calycode/cli": patch
+'@calycode/core': patch
+'@calycode/cli': patch
 ---
 
 feat: improvements to the documentation generation, added changelog links, full-text search, pagination plugin, terminaly plugin, flexible callouts plugin, dark mode support and mermaid support plugins
+refactor: rearranged the repo to be more like a proper turbo powered monorepo. Build times are much faster as before...
+refactor: adjustments to the github workflows to match turborepo (without remote cache)

.github/workflows/add-docs-to-release.yml

@@ -24,12 +24,13 @@ jobs:
       - uses: actions/setup-node@v4
         with:
           node-version: 20.x
+          cache: 'pnpm'
 
       - name: Install packages
-        run: pnpm install
+        run: pnpm install --frozen-lockfile
 
       - name: Build packages
-        run: pnpm build:packages
+        run: pnpm build
 
       - name: Build Docs
         run: pnpm build:docs

.github/workflows/release.yml

@@ -26,25 +26,26 @@ jobs:
            uses: actions/setup-node@v4
            with:
               node-version: 20.x
+              cache: 'pnpm'
               registry-url: 'https://registry.npmjs.org'
               scope: '@calycode'
               always-auth: true
            env:
               NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
          - name: Install dependencies
-           run: pnpm install
+           run: pnpm install --frozen-lockfile
 
          - name: Build packages
-           run: pnpm build:packages
+           run: pnpm build
 
          - name: Publish to npm
            id: changesets
            uses: changesets/action@v1
            with:
               commit: 'changeset-release'
               title: 'Release Version'
-              publish: pnpm -r publish --access restricted
+              publish: pnpm -r publish
            env:
               GITHUB_TOKEN: ${{ secrets.CHANGESETS_GH_TOKEN }}
               NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

.github/workflows/upload-docs.yml

@@ -22,17 +22,15 @@ jobs:
            uses: actions/setup-node@v4
            with:
               node-version: 20.x
+              cache: 'pnpm'
               registry-url: 'https://registry.npmjs.org'
               scope: '@calycode'
               always-auth: true
            env:
               NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
 
          - name: Install dependencies
-           run: pnpm install
-
-         - name: Build packages
-           run: pnpm build:packages
+           run: pnpm install --frozen-lockfile
 
          - name: Update the docs
            run: pnpm build:docs

.gitignore

@@ -30,3 +30,5 @@ project-plan.md
 *.tsbuildinfo
 calyInstance.config.js
 calyInstance.test.setup.json
+
+**/.turbo/

docs/commands/export-backup.md

@@ -24,12 +24,9 @@ Usage: xano export-backup [options]
 Backup Xano Workspace via Metadata API
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value
-                           provided at the setup command.
-  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on
-                           Xano interface.
-  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano
-                           Interface.
+  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value provided at the setup command.
+  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on Xano interface.
+  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano Interface.
   --print-output-dir       Expose usable output path for further reuse.
   -h, --help               display help for command
 ```

docs/commands/generate-code.md

@@ -31,24 +31,17 @@ $ xano generate-code [options]
 $ xano generate-code --help
 Usage: xano generate-code [options]
 
-Create a library based on the OpenAPI specification. If the openapi specification has not yet been generated,
-this will generate that as well as the first step.
+Create a library based on the OpenAPI specification. If the openapi specification has not yet been generated, this will generate that as well as the first step.
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value
-                           provided at the setup command.
-  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on
-                           Xano interface.
-  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano
-                           Interface.
+  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value provided at the setup command.
+  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on Xano interface.
+  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano Interface.
   --group <name>           API group name. Same as on Xano Interface.
   --all                    Regenerate for all API groups in the workspace / branch of the current context.
   --print-output-dir       Expose usable output path for further reuse.
-  --generator <generator>  Generator to use, see all options at:
-                           https://openapi-generator.tech/docs/generators
-  --args <args>            Additional arguments to pass to the generator. See
-                           https://openapi-generator.tech/docs/usage#generate
-  --debug                  Specify this flag in order to allow logging. Logs will appear in output/_logs.
-                           Default: false
+  --generator <generator>  Generator to use, see all options at: https://openapi-generator.tech/docs/generators
+  --args <args>            Additional arguments to pass to the generator. See https://openapi-generator.tech/docs/usage#generate
+  --debug                  Specify this flag in order to allow logging. Logs will appear in output/_logs. Default: false
   -h, --help               display help for command
 ```

docs/commands/generate-oas.md

@@ -28,12 +28,9 @@ Usage: xano generate-oas [options]
 Update and generate OpenAPI spec(s) for the current context.
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value
-                           provided at the setup command.
-  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on
-                           Xano interface.
-  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano
-                           Interface.
+  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value provided at the setup command.
+  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on Xano interface.
+  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano Interface.
   --group <name>           API group name. Same as on Xano Interface.
   --all                    Regenerate for all API groups in the workspace / branch of the current context.
   --print-output-dir       Expose usable output path for further reuse.

docs/commands/generate-repo.md

@@ -32,12 +32,9 @@ Process Xano workspace into repo structure
 Options:
   --input <file>           workspace yaml file
   --output <dir>           output directory (overrides config)
-  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value
-                           provided at the setup command.
-  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on
-                           Xano interface.
-  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano
-                           Interface.
+  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value provided at the setup command.
+  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on Xano interface.
+  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano Interface.
   --print-output-dir       Expose usable output path for further reuse.
   --fetch                  Specify this if you want to fetch the workspace schema from Xano
   -h, --help               display help for command

docs/commands/generate-xs-repo.md

@@ -24,12 +24,9 @@ Usage: xano generate-xs-repo [options]
 Process Xano workspace into repo structure
 
 Options:
-  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value
-                           provided at the setup command.
-  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on
-                           Xano interface.
-  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano
-                           Interface.
+  --instance <instance>    The instance name. This is used to fetch the instance configuration. The value provided at the setup command.
+  --workspace <workspace>  The workspace name. This is used to fetch the workspace configuration. Same as on Xano interface.
+  --branch <branch>        The branch name. This is used to select the branch configuration. Same as on Xano Interface.
   --print-output-dir       Expose usable output path for further reuse.
   -h, --help               display help for command
 ```