{"_id":"@alternatefutures/next","_rev":"3-0f512cc3df8ccb1201d6846f6485fe99","name":"@alternatefutures/next","dist-tags":{"latest":"0.1.0"},"versions":{"0.1.0":{"name":"@alternatefutures/next","version":"0.1.0","keywords":["nextjs","next","alternatefutures","server-side","edge","serverless"],"license":"MIT","_id":"@alternatefutures/next@0.1.0","maintainers":[{"name":"alternatefutures","email":"system@alternatefutures.ai"}],"homepage":"https://github.com/alternatefutures/af-cloud-next/#readme","bugs":{"url":"https://github.com/alternatefutures/af-cloud-next/issues"},"bin":{"af-next":"dist/index.js"},"dist":{"shasum":"da4ad162cf857a4a28b79ab3eb691264e0ab51cf","tarball":"https://registry.npmjs.org/@alternatefutures/next/-/next-0.1.0.tgz","fileCount":72,"integrity":"sha512-E5iq3CdmSv+Lz5zB+BBtqK3cKTRL44/eZvMq1YNSJ5aQPJej6OxjwoPDcESrP5axCz6OXjAA8+tnyxxZuuzXgg==","signatures":[{"sig":"MEUCIGZEQPTRJ8sJxR39yNB/LYMFlcVMg3CCevCqLiV1ar5BAiEAoTuFM1ovd6Jx1RnhWOMkhiR0t5XVRvEjOTUv3f5hecQ=","keyid":"SHA256:DhQ8wR5APBvFHLF/+Tc+AYvPOdTpcIDqOhxsBHRwC7U"}],"unpackedSize":67150},"main":"./dist/cli.js","type":"module","types":"./dist/cli.d.ts","module":"./dist/cli.js","engines":{"node":">=18"},"gitHead":"9ebbd7da2f4bf1907557f9104e0824b6e3e10cd9","scripts":{"lint":"eslint 'src/**/*.{js,ts}'","build":"tsc","format":"prettier . --write","prepare":"husky","format:check":"prettier . --check"},"_npmUser":{"name":"alternatefutures","email":"system@alternatefutures.ai"},"repository":{"url":"git+https://github.com/alternatefutures/af-cloud-next.git","type":"git"},"_npmVersion":"10.5.0","description":"Deploy your server-side Next.js application on AlternateFutures","directories":{},"lint-staged":{"*":["prettier . --check","eslint"]},"_nodeVersion":"20.12.2","dependencies":{"ora":"^8.0.1","boxen":"^7.1.1","chalk":"^5.3.0","semver":"^7.6.2","esbuild":"^0.24.0","prompts":"^2.4.2","commander":"^12.0.0","ansi-escapes":"^7.0.0","update-notifier":"^7.0.0","update-notifier-cjs":"^5.1.6","@fleek-platform/next-on-fleek":"1.15.5","@alternatefutures/functions-esbuild-config":"^0.1.0"},"_hasShrinkwrap":false,"devDependencies":{"husky":"^9.0.11","eslint":"^9.2.0","prettier":"^3.2.5","@eslint/js":"^9.2.0","typescript":"^5.4.5","@types/node":"^20.12.11","lint-staged":"^15.2.2","@types/semver":"^7.5.8","@types/prompts":"^2.4.9","@commitlint/cli":"^19.3.0","typescript-eslint":"^7.8.0","@commitlint/config-conventional":"^19.2.2"},"_npmOperationalInternal":{"tmp":"tmp/next_0.1.0_1760030498678_0.21845012710783562","host":"s3://npm-registry-packages-npm-production"}}},"time":{"created":"2025-10-09T17:21:38.525Z","modified":"2026-04-07T01:26:07.547Z","0.1.0":"2025-10-09T17:21:38.866Z"},"bugs":{"url":"https://github.com/alternatefutures/af-cloud-next/issues"},"license":"MIT","homepage":"https://github.com/alternatefutures/af-cloud-next/#readme","keywords":["nextjs","next","alternatefutures","server-side","edge","serverless"],"repository":{"url":"git+https://github.com/alternatefutures/af-cloud-next.git","type":"git"},"description":"Deploy your server-side Next.js application on AlternateFutures","maintainers":[{"email":"hayk@alternatefutures.ai","name":"alternatehayk"},{"email":"system@alternatefutures.ai","name":"system-af"}],"readme":"# ⚡️AlternateFutures Next Adapter\n\n[![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-blue.svg)](https://conventionalcommits.org)\n\nThe AlternateFutures Next.js adapter allows you to deploy your server-side Next.js application on AlternateFutures.\n\n# Installation\n\n- **npm**\n\n```bash\nnpm install @alternatefutures/next\n```\n\n- **pnpm**\n\n```bash\npnpm install @alternatefutures/next\n```\n\n# Usage\n\nTo build and prepare your Next.js application for deployment on AlternateFutures, follow these steps:\n\n1. **Configure Edge Runtime**\n   Add the following code to any routes that run server-side code to ensure they run on the edge:\n\n```typescript\nexport const runtime = 'edge';\n```\n\n2. **Build**\n\nUse the AlternateFutures Next.js adapter to build and deploy your application via the command line:\n\n```sh\nnpx af-next build\n# or if installed globally\naf-next build\n```\n\nIf you are running the command outside of your project's root dir, you can set the path to it with the project path flag `-p`/`--projectPath`:\n\n```sh\naf-next build -p path/to/my/repo\n```\n\nThe `build` command supports several options to customize the build and deployment process:\n\n- `-p, --project-path <path>`: The path to your Next.js project's root directory. Defaults to the path where the command is run.\n- `-s, --skipBuild`: Skip building the Next.js app before deployment, useful if you want to build the application yourself due to any possible extra steps. Defaults to `false`.\n- `-i, --skipInstallation`: Skip installing the dependencies. Defaults to `false`.\n- `-c, --clean`: Clean previous build artifacts before building.\n- `-v, --verbose`: Enable verbose logging.\n\n3. **Deploy your function:**\n\nUse the [AlternateFutures CLI](https://www.npmjs.com/package/@alternatefutures/cli) to deploy your function:\n\n```sh\nfleek functions deploy --noBundle --name '<name of your function>' --path .fleek/dist/index.js\n```\n\n# Release Process\n\nThis project follows SemVer for versioning. Here's how to release a new version:\n\n1. **Update Version Number**: Bump the version number in package.json using npm version (patch/minor/major). This will update the version number in package.json and create a new Git tag.\n\n```bash\npnpm version patch\n```\n\n2. **Push Changes and Tags**\n\n```bash\ngit push origin main --follow-tags\n```\n\n3. **GitHub Actions Automation**: A GitHub Actions workflow automatically publishes the package to npm when a new tag is pushed.\n\n# Contributing\n\nThanks for considering contributing to our project!\n\n## How to Contribute\n\n1. Fork the repository.\n2. Create a new branch: `git checkout -b feature-branch-name`.\n3. Make your changes.\n4. Commit your changes using conventional commits.\n5. Push to your fork and submit a pull request.\n\n## Commit Guidelines\n\nWe use [Conventional Commits](https://www.conventionalcommits.org/) for our commit messages:\n\n- `test`: 💍 Adding missing tests\n- `feat`: 🎸 A new feature\n- `fix`: 🐛 A bug fix\n- `chore`: 🤖 Build process or auxiliary tool changes\n- `docs`: ✏️ Documentation only changes\n- `refactor`: 💡 A code change that neither fixes a bug or adds a feature\n- `style`: 💄 Markup, white-space, formatting, missing semi-colons...\n","readmeFilename":"README.md"}