chore: code cleanup

Author: darcyclarke

.github/workflows/auto-publish.yml

@@ -24,9 +24,6 @@ jobs:
         with:
           node-version: '18'
           registry-url: 'https://registry.npmjs.org'
-          
-      - name: Setup Docker Buildx
-        uses: docker/setup-buildx-action@v3
 
       - name: Install dependencies
         run: npm install

.github/workflows/test.yml

@@ -17,9 +17,6 @@ jobs:
         uses: actions/setup-node@v4
         with:
           node-version: '18'
-          
-      - name: Setup Docker Buildx
-        uses: docker/setup-buildx-action@v3
 
       - name: Install dependencies
         run: npm install

.npmignore

@@ -0,0 +1,6 @@
+vlt-lock.json
+vlt.json
+contributing.md
+packages/
+scripts/
+.github/

CONTRIBUTING.md

@@ -0,0 +1,57 @@
+# Contributing
+
+## Development
+
+### Prerequisites
+
+- Node.js 18+
+- `tar` command (available on macOS/Linux by default)
+- npm account with publishing permissions
+
+### Scripts
+
+```bash
+# Check for new versions
+npm run check-version
+
+# Extract binaries from GitHub releases
+npm run extract-binaries
+
+# Build everything (check + extract)
+npm run build
+
+# Test all binaries
+npm run test
+
+# Publish all packages to npm
+npm run publish-all
+```
+
+### Versioning
+
+Set the versions across all packages & update the root's dependency specs
+
+```bash
+$ npm run version --ws --iwr 0.24.1-pre.2
+```
+
+> Note: `npm` will error because of the optional deps `"os"` & `"cpu"` definitions. You can safely ignore this error as the operation will still successfully update the `package.json
+
+### Publishing
+
+Setting a `--tag` may not be desired depending on if its a prerelease
+
+```bash
+$ npm publish --ws --iwr --tag latest --access public
+```
+
+### GitHub Actions
+
+Two workflows are included:
+
+1. **`auto-publish.yml`**: Runs daily and on pushes to main, automatically publishes new versions
+2. **`test.yml`**: Manual testing workflow that builds but doesn't publish
+
+To set up automated publishing, add these secrets to your GitHub repository:
+
+- `NPM_TOKEN`: Your npm authentication token with publish permissions

README.md

@@ -2,7 +2,7 @@
 
 A package wrapper for [libsql-server](https://github.com/tursodatabase/libsql) (`sqld`) with platform-specific binaries.
 
-This package automatically downloads and publishes the latest `libsql-server` releases from the official Docker container, making them available as npm packages with platform-specific binaries.
+This package automatically downloads and publishes the latest `libsql-server` releases from the [official GitHub releases](https://github.com/tursodatabase/libsql/releases?q=libsql-server-), making them available as npm packages with platform-specific binaries.
 
 ## Installation
 
@@ -42,150 +42,34 @@ vlx sqld --help
 vlx sqld --db-path ./my-database.db
 ```
 
-### Programmatic API
-
-```javascript
-const sqld = require('sqld');
-
-// Execute sqld synchronously
-try {
-  const result = sqld.execSync(['--help']);
-  console.log(result.toString());
-} catch (error) {
-  console.error('Error:', error.message);
-}
-
-// Execute sqld asynchronously
-const child = sqld.exec(['--db-path', './my-database.db']);
-
-child.stdout.on('data', (data) => {
-  console.log('stdout:', data.toString());
-});
-
-child.stderr.on('data', (data) => {
-  console.error('stderr:', data.toString());
-});
-
-child.on('exit', (code) => {
-  console.log('Process exited with code:', code);
-});
-
-// Get the binary path
-const binaryPath = sqld.getBinaryPath();
-console.log('Binary located at:', binaryPath);
-
-// Get the platform package name
-const platformPackage = sqld.getPlatformPackage();
-console.log('Using platform package:', platformPackage);
-```
-
 ## How It Works
 
-This project uses a multi-package approach:
+This project uses a simple platform-specific binary distribution approach:
 
-1. **Main Package (`sqld`)**: Contains the Node.js wrapper and CLI interface
-2. **Platform Packages**: Contains the actual binaries for each platform:
-   - `@sqld/darwin-arm64`
-   - `@sqld/darwin-x64`
-   - `@sqld/linux-arm64`
-   - `@sqld/linux-x64`
+1. **Platform Detection**: The package manager automatically installs only the compatible platform package based on your OS and architecture
+2. **Direct Binary Access**: Each platform package directly provides the `sqld` binary through its `bin` field
+3. **No Wrapper**: No JavaScript wrapper or bootstrap code - the platform packages directly expose the native `sqld` binary
 
-The main package declares the platform packages as optional dependencies. When you install `sqld`, your package manager will only install the package that matches your current platform.
+### Automated Updates
 
-## Automated Updates
+The project automatically checks for new `libsql-server` releases daily using GitHub Actions:
 
-This project automatically checks for new `libsql-server` releases daily using GitHub Actions:
-
-1. **Daily Check**: Runs at 9 AM UTC to check for new releases
-2. **Binary Extraction**: Downloads the Docker container and extracts platform-specific binaries
+1. **Daily Check**: Runs at 9 AM UTC to check for new releases from the [libsql GitHub repository](https://github.com/tursodatabase/libsql/releases?q=libsql-server-)
+2. **Binary Extraction**: Downloads platform-specific tarballs and extracts the `sqld` binaries
 3. **Testing**: Verifies that all binaries work correctly
-4. **Publishing**: Automatically publishes new versions to `npmjs.com`
+4. **Publishing**: Automatically publishes new versions to npm
 5. **Git Commit**: Commits the updated binaries to the repository
 
-## Development
-
-### Prerequisites
-
-- Node.js 18+
-- `vlt` (`npm i -g vlt`)
-
-### Scripts
-
-```bash
-# Check for new versions
-vlr check-version
-
-# Extract binaries from Docker containers
-vlr extract-binaries
-
-# Build everything (check + extract)
-vlr build
-
-# Test all binaries
-clr test
-
-# Publish all packages to npm
-vlr publish-all
-```
-
-### Manual Testing
-
-You can test the build process manually:
-
-```bash
-# Install dependencies
-vlt install
-
-# Extract the latest binaries
-vlr extract-binaries
-
-# Test that everything works
-vlr test
-
-# Test the CLI
-./bin/sqld --help
-```
-
-### GitHub Actions
-
-Two workflows are included:
-
-1. **`auto-publish.yml`**: Runs daily and on pushes to main, automatically publishes new versions
-2. **`test.yml`**: Manual testing workflow that builds but doesn't publish
-
-To set up automated publishing, add these secrets to your GitHub repository:
-
-- `NPM_TOKEN`: Your npm authentication token with publish permissions
-
-## Project Structure
-
-```
-sqld/
-├── package.json              # Main package configuration
-├── lib/index.js              # Node.js API
-├── bin/sqld                  # CLI wrapper
-├── scripts/
-│   ├── check-version.js      # Check for new releases
-│   ├── extract-binaries.js   # Extract binaries from Docker
-│   ├── build.js              # Build orchestration
-│   ├── publish-all.js        # Publish all packages
-│   └── test.js               # Test all binaries
-├── packages/
-│   ├── darwin-arm64/         # macOS ARM64 package
-│   ├── darwin-x64/           # macOS x64 package
-│   ├── linux-arm64/          # Linux ARM64 package
-│   └── linux-x64/            # Linux x64 package
-└── .github/workflows/        # GitHub Actions
-```
+The project uses the following release artifacts for each platform:
+- **macOS ARM64**: `libsql-server-aarch64-apple-darwin.tar.xz`
+- **macOS x64**: `libsql-server-x86_64-apple-darwin.tar.xz`
+- **Linux ARM64**: `libsql-server-aarch64-unknown-linux-gnu.tar.xz`
+- **Linux x64**: `libsql-server-x86_64-unknown-linux-gnu.tar.xz`
 
 ## License
 
 MIT
 
-## Contributing
-
-Contributions are welcome! Please feel free to submit a Pull Request.
-
 ## Related Projects
 
 - [libsql](https://github.com/tursodatabase/libsql) - The original libSQL project