sapper-iq 1.1.36 → 1.1.38

package/.github/workflows/ci.yml

@@ -1,35 +0,0 @@
-name: CI
-
-on:
-  push:
-    branches: [ main ]
-  pull_request:
-    branches: [ main ]
-
-jobs:
-  test:
-    runs-on: ubuntu-latest
-    strategy:
-      matrix:
-        node-version: [16.x, 18.x, 20.x]
-
-    steps:
-    - name: Checkout code
-      uses: actions/checkout@v4
-
-    - name: Use Node.js ${{ matrix.node-version }}
-      uses: actions/setup-node@v4
-      with:
-        node-version: ${{ matrix.node-version }}
-        cache: 'npm'
-
-    - name: Install dependencies
-      run: npm ci
-
-    - name: Run tests
-      run: npm test --if-present
-
-    - name: Check if sapper runs
-      run: |
-        chmod +x sapper.mjs
-        timeout 5s node sapper.mjs --help || true

package/.github/workflows/publish.yml

@@ -1,46 +0,0 @@
-name: Publish to NPM
-
-on:
-  release:
-    types: [published]
-  push:
-    tags:
-      - 'v*'
-
-jobs:
-  publish:
-    runs-on: ubuntu-latest
-    steps:
-      - name: Checkout code
-        uses: actions/checkout@v4
-
-      - name: Setup Node.js
-        uses: actions/setup-node@v4
-        with:
-          node-version: '18'
-          registry-url: 'https://registry.npmjs.org'
-
-      - name: Install dependencies
-        run: npm ci
-
-      - name: Run tests (if any)
-        run: npm test --if-present
-
-      - name: Publish to NPM
-        run: npm publish
-        env:
-          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-
-      - name: Create GitHub Release
-        if: startsWith(github.ref, 'refs/tags/v')
-        uses: actions/create-release@v1
-        env:
-          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
-        with:
-          tag_name: ${{ github.ref }}
-          release_name: Release ${{ github.ref }}
-          body: |
-            ## Changes in this release
-            - Auto-generated release from tag ${{ github.ref }}
-          draft: false
-          prerelease: false

package/PUBLISHING.md

@@ -1,148 +0,0 @@
-# Publishing Sapper to NPM
-
-This guide explains how to publish Sapper to npm registry manually.
-
-## Prerequisites
-
-1. **npm account** - Create at [npmjs.com](https://npmjs.com)
-2. **npm login** - Run `npm login` in terminal
-3. **Package name available** - Check if "sapper" is available on npm
-
-## Step-by-Step Publishing Process
-
-### 1. Verify Package Configuration
-
-Check `package.json` has correct information:
-```json
-{
-  "name": "sapper",
-  "version": "1.0.0",
-  "main": "sapper.mjs",
-  "bin": {
-    "sapper": "./sapper.mjs"
-  },
-  "type": "module"
-}
-```
-
-### 2. Make Executable
-
-Ensure the main file is executable:
-```bash
-chmod +x sapper.mjs
-```
-
-### 3. Test Locally
-
-Test the package locally before publishing:
-```bash
-npm link
-sapper --version  # Test if it works
-npm unlink -g sapper  # Clean up
-```
-
-### 4. Check Package Contents
-
-See what files will be published:
-```bash
-npm pack --dry-run
-```
-
-### 5. Login to NPM
-
-```bash
-npm login
-# Enter username, password, email, and 2FA code
-```
-
-### 6. Publish
-
-```bash
-npm publish
-```
-
-If successful, you'll see:
-```
-+ sapper@1.0.0
-```
-
-### 7. Verify Installation
-
-Test global installation:
-```bash
-npm install -g sapper
-sapper --version
-```
-
-## Publishing Updates
-
-### For patch updates (1.0.0 → 1.0.1):
-```bash
-npm version patch
-git push --follow-tags
-npm publish
-```
-
-### For minor updates (1.0.0 → 1.1.0):
-```bash
-npm version minor  
-git push --follow-tags
-npm publish
-```
-
-### For major updates (1.0.0 → 2.0.0):
-```bash
-npm version major
-git push --follow-tags
-npm publish
-```
-
-## Troubleshooting
-
-### Package name taken
-If "sapper" is taken, try alternatives:
-- `sapper-ai`
-- `sapper-cli`  
-- `ai-sapper`
-
-Update `package.json` name field accordingly.
-
-### Authentication errors
-```bash
-npm logout
-npm login
-```
-
-### Permission errors
-Check if you have publish rights to the package name.
-
-### Version conflicts
-Each publish must have a unique version number. Increment version in `package.json`.
-
-## Post-Publish Steps
-
-1. **Verify on npmjs.com** - Visit `https://npmjs.com/package/sapper`
-2. **Test installation** - `npm install -g sapper`
-3. **Update README** - Add npm installation instructions
-4. **Tag release on GitHub** - Create release tag matching npm version
-
-## NPM Commands Reference
-
-- `npm whoami` - Check logged in user
-- `npm view sapper` - View package info
-- `npm unpublish sapper@1.0.0` - Remove specific version (within 24hrs)
-- `npm deprecate sapper@1.0.0 "reason"` - Mark version as deprecated
-- `npm owner ls sapper` - List package owners
-
-## GitHub Integration
-
-After publishing, users can install via:
-- `npm install -g sapper` (from npm registry)  
-- `npm install -g git+https://github.com/aledanee/sapper.git` (from GitHub)
-
-Keep both npm and GitHub versions synchronized.
-
-
-
-
-git add . && git commit -m "Add specialized Node.js/PostgreSQL prompts with use cases" && npm version patch && npm publish