chore(repo): monorepo transition

.cursor/mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "nx-mcp": {
+      "command": "npx",
+      "args": ["-y", "nx-mcp@latest"]
+    }
+  }
+}

.cursorrules

@@ -0,0 +1,162 @@
+# Cursor Rules for Supabase JS Libraries Monorepo
+
+You are working in a unified Nx monorepo that consolidates all Supabase JavaScript client libraries. This migration from 6 separate repositories addresses maintenance overhead, dependency duplication, and release coordination challenges.
+
+## Repository Context
+
+This monorepo contains 6 JavaScript/TypeScript libraries previously maintained as separate repositories:
+- `packages/core/supabase-js` - Main isomorphic client combining all libraries (@supabase/supabase-js)
+- `packages/core/auth-js` - Authentication client (@supabase/auth-js)
+- `packages/core/functions-js` - Edge Functions client (@supabase/functions-js)
+- `packages/core/postgrest-js` - PostgREST database client (@supabase/postgrest-js)
+- `packages/core/realtime-js` - Real-time subscriptions client (@supabase/realtime-js)
+- `packages/core/storage-js` - File storage client (@supabase/storage-js)
+
+## Key Principles
+
+1. **Zero Breaking Changes**: All migrations and changes must maintain full backward compatibility for consumers
+2. **Fixed Version Mode**: All packages share the same version number and are released together
+3. **Workspace Dependencies**: Internal dependencies use `*` which Nx replaces with actual versions during release
+4. **Affected Testing**: Always use `nx affected` commands to test only what changed
+5. **Conventional Commits**: Use conventional commit format for automated versioning and changelogs
+
+## Common Commands
+
+### Building
+- Build all: `nx run-many --target=build --all`
+- Build specific: `nx build auth-js`
+- Build affected: `nx affected --target=build`
+- Watch mode: `nx build auth-js --watch`
+
+### Testing
+- Test all: `nx run-many --target=test --all`
+- Test specific: `nx test auth-js`
+- Test affected: `nx affected --target=test`
+- Integration tests: `nx run-many --target=test:integration --all`
+
+### Code Quality
+- Lint all: `nx run-many --target=lint --all`
+- Format: `nx format`
+- Check format: `nx format:check`
+
+### Analysis
+- Dependency graph: `nx graph`
+- Show projects: `nx show projects`
+- Affected graph: `nx affected --graph`
+
+## Development Patterns
+
+### Cross-Library Changes
+When making changes that affect multiple libraries:
+1. Make all changes in a single PR
+2. Update tests in both source library and integration tests in supabase-js
+3. Use `nx affected --target=test` to verify all impacts
+4. Commit with clear scope: `fix(realtime-js): resolve connection issue`
+
+### Adding New Features
+1. Implement in the specific library under `packages/core/[library-name]`
+2. Add comprehensive unit tests in the library's `test/` directory
+3. If it affects supabase-js, add integration tests there
+4. Run `nx affected --target=test` before committing
+
+### Quick Fixes
+Even for single-library fixes:
+1. Use conventional commit: `fix(storage-js): correct upload timeout`
+2. All packages will be versioned together (fixed mode)
+3. Run `nx affected --target=test`
+4. Changes ship together in next release
+
+## TypeScript Configuration
+
+The workspace uses strict TypeScript settings:
+- Target: ES2022
+- Module: NodeNext
+- Strict mode enabled
+- Isolated modules for performance
+- Composite projects for incremental builds
+
+## Testing Infrastructure
+
+### Unit Tests
+- Located in each library's `test/` directory
+- Use Jest as test runner
+- Mock external dependencies
+
+### Integration Tests
+- Libraries with external services (auth-js, storage-js) use Docker
+- Docker Compose configs in `infra/` directories
+- Run with: `npm run test:infra` from library directory
+
+### Cross-Platform Tests
+The main supabase-js tests against:
+- Node.js
+- Next.js
+- Expo (React Native)
+- Bun runtime
+- Deno runtime
+- Browser environment
+
+## File Structure Conventions
+
+```
+packages/core/[library-name]/
+├── src/           # Source code
+├── test/          # Test files
+├── dist/          # Build output (gitignored)
+├── package.json   # Package configuration
+└── tsconfig.json  # TypeScript config
+```
+
+## Important Notes
+
+- **Different Default Branches**: Original repos used either `master` or `main` - be aware when referencing history
+- **Package Names**: All packages maintain original npm names (@supabase/[package-name])
+- **Shared Code**: Extract common patterns (HTTP client, error handling) to shared packages when identified
+- **Docker Required**: Integration tests for auth-js and storage-js require Docker to be running
+
+## Release Process
+
+### Fixed Version Release
+All packages released with same version:
+```bash
+nx release              # Interactive release
+nx release --dry-run    # Preview changes
+nx release --yes        # CI automation
+```
+
+### Internal Dependencies
+```json
+// packages/core/supabase-js/package.json
+"dependencies": {
+  "@supabase/auth-js": "*",
+  "@supabase/realtime-js": "*",
+  "@supabase/functions-js": "*",
+  "@supabase/storage-js": "*",
+  "@supabase/postgrest-js": "*"
+}
+```
+The `*` is replaced with actual version during release.
+
+## Code Style
+
+- Use Prettier for formatting (config in .prettierrc)
+- Follow existing patterns in each library
+- Maintain consistency across the monorepo
+- Document public APIs with JSDoc comments
+
+## Common Pitfalls to Avoid
+
+1. Don't hardcode version numbers for internal dependencies
+2. Don't make breaking changes to public APIs
+3. Don't forget to run affected tests before committing
+4. Don't mix unrelated changes in a single commit
+5. Don't bypass the Nx build system by running npm scripts directly for cross-library work
+
+## When Making Suggestions
+
+1. Always consider the monorepo structure - changes might affect multiple packages
+2. Use Nx commands rather than npm/yarn directly for workspace operations
+3. Suggest running affected tests, not all tests, for better performance
+4. Remember that all packages version together in fixed mode
+5. Consider Docker requirements for integration tests
+6. Maintain backward compatibility at all costs

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,105 @@
+name: "\U0001F41E Bug report"
+description: Report an issue with a Supabase JS Library
+labels: [bug]
+type: Bug
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: bug-description
+    attributes:
+      label: Describe the bug
+      description: A clear and concise description of what the bug is. If you intend to submit a PR for this issue, tell us in the description. Thanks!
+      placeholder: I am doing ... What I expect is ... What actually happening is ...
+    validations:
+      required: true
+  - type: dropdown
+    id: supabase-library
+    attributes:
+      label: Library affected
+      description: Select the library that you think is affected by the bug
+      options:
+        - supabase-js
+        - auth-js
+        - postgrest-js
+        - realtime-js
+        - storage-js
+        - functions-js
+        - unsure/all/other
+    validations:
+      required: true
+  - type: input
+    id: reproduction
+    attributes:
+      label: Reproduction
+      description: If possible, please provide a link to a repo that can reproduce the problem you ran into. A [minimal reproduction](https://stackoverflow.com/help/minimal-reproducible-example) is very helpful. ([Why?](https://antfu.me/posts/why-reproductions-are-required)). If a report is vague (e.g. just a generic error message) and has no reproduction, it will receive a "needs reproduction" label. If no reproduction is provided after 7 days, it will be closed.
+      placeholder: Reproduction URL
+    validations:
+      required: false
+  - type: textarea
+    id: reproduction-steps
+    attributes:
+      label: Steps to reproduce
+      description: Please provide any reproduction steps that may need to be described.
+      placeholder: Run `npm install` followed by `npm run dev`
+  - type: textarea
+    id: system-info
+    attributes:
+      label: System Info
+      description: Output of `npx envinfo --system --npmPackages '{supabase,@supabase/*}' --binaries --browsers`
+      render: shell
+      placeholder: System, Binaries, Browsers
+    validations:
+      required: true
+  - type: dropdown
+    id: package-manager
+    attributes:
+      label: Used Package Manager
+      description: Select the used package manager
+      options:
+        - npm
+        - yarn
+        - pnpm
+        - bun
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Logs
+      description: |
+        Optional if provided reproduction. It's very helpful to provide the log text instead of a screenshot.
+
+        Provide the error log here in the format below.
+
+        ````
+        <details>
+        <summary>Click to expand!</summary>
+
+        ```shell
+        // paste the log text here
+        ```
+        </details>
+        ````
+  - type: checkboxes
+    id: checkboxes
+    attributes:
+      label: Validations
+      description: Before submitting the issue, please make sure you do the following
+      options:
+        - label: Follow our [Code of Conduct](https://github.com/supabase/.github/blob/main/CODE_OF_CONDUCT.md)
+          required: true
+        - label: Read the [Contributing Guidelines](https://github.com/supabase/js-client-libs/blob/main/docs/CONTRIBUTING.md).
+          required: true
+        - label: Read the [docs](https://supabase.com/docs/reference/javascript/introduction).
+          required: true
+        - label: Check that there isn't [already an issue](https://github.com/supabase/js-client-libs/issues) that reports the same bug to avoid creating a duplicate.
+          required: true
+        - label: Make sure this is a Supabase JS Library issue and not an issue with the Supabase platform. If it's a Supabase platform related bug, it should likely be reported to [supabase/supabase](https://github.com/supabase/supabase) instead.
+          required: true
+        - label: Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/supabase/js-client-libs/discussions) or join our [Discord Chat Server](https://discord.supabase.com//).
+          required: true
+        - label: The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.
+          required: true

.github/ISSUE_TEMPLATE/docs.yml

@@ -0,0 +1,43 @@
+name: "\U0001F4DA Documentation"
+description: Suggest an update to the Supabase JS Libraries documentation
+labels: [documentation]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this issue!
+  - type: checkboxes
+    id: documentation_is
+    attributes:
+      label: Documentation is
+      options:
+        - label: Missing
+        - label: Outdated
+        - label: Confusing
+        - label: Not sure?
+  - type: textarea
+    id: description
+    attributes:
+      label: Explain in Detail
+      description: A clear and concise description of your suggestion. If you intend to submit a PR for this issue, tell us in the description. Thanks!
+      placeholder: The description of ... is not clear. I thought it meant ... but it wasn't.
+    validations:
+      required: true
+  - type: textarea
+    id: suggestion
+    attributes:
+      label: Your Suggestion for Changes
+    validations:
+      required: false
+  - type: input
+    id: docs-url
+    attributes:
+      label: Documentation URL
+      description: If you have a URL to the problematic docs, please provide it.
+      placeholder: Documentation URL
+  - type: textarea
+    id: reproduction-steps
+    attributes:
+      label: Steps to reproduce
+      description: Please provide any reproduction steps that may need to be described.
+      placeholder: Run `npm install` followed by `npm run dev`

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,48 @@
+name: "\U0001F680 New feature proposal"
+description: Propose a new feature to be added to the Supabase JS Libraries
+labels: ['enhancement']
+type: Feature
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for your interest in the project and taking the time to fill out this feature report!
+  - type: textarea
+    id: feature-description
+    attributes:
+      label: Description
+      description: 'Clear and concise description of the problem. Please make the reason and usecases as detailed as possible. If you intend to submit a PR for this issue, tell us in the description. Thanks!'
+      placeholder: As a developer using the Supabase JS Libraries I want [goal / wish] so that [benefit].
+    validations:
+      required: true
+  - type: textarea
+    id: suggested-solution
+    attributes:
+      label: Suggested solution
+      description: 'In the library [xy] we could provide following implementation...'
+    validations:
+      required: true
+  - type: textarea
+    id: alternative
+    attributes:
+      label: Alternative
+      description: Clear and concise description of any alternative solutions or features you've considered.
+  - type: textarea
+    id: additional-context
+    attributes:
+      label: Additional context
+      description: Any other context or screenshots about the feature request here.
+  - type: checkboxes
+    id: checkboxes
+    attributes:
+      label: Validations
+      description: Before submitting the issue, please make sure you do the following
+      options:
+        - label: Follow our [Code of Conduct](https://github.com/supabase/.github/blob/main/CODE_OF_CONDUCT.md)
+          required: true
+        - label: Read the [Contributing Guidelines](https://github.com/supabase/js-client-libs/blob/main/docs/CONTRIBUTING.md).
+          required: true
+        - label: Read the [docs](https://supabase.com/docs/reference/javascript/introduction).
+          required: true
+        - label: Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
+          required: true