belazywithreact 0.1.0__tar.gz

belazywithreact-0.1.0/.gitignore

@@ -0,0 +1,34 @@
+__pycache__/
+*.py[cod]
+.pytest_cache/
+.coverage
+htmlcov/
+.venv/
+build/
+dist/
+*.egg-info/
+venv/
+env/
+.*-venv/
+.tox/
+.nox/
+.ruff_cache/
+.mypy_cache/
+.coverage.*
+coverage.xml
+node_modules/
+.env
+.env.*
+!.env.example
+*.pem
+*.key
+.pypirc
+.npmrc
+.idea/
+.vscode/
+.DS_Store
+Thumbs.db
+*.log
+# Existing local generated app: preserved, excluded from the package repository.
+/lazy/
+/.release-check/

belazywithreact-0.1.0/CONTRIBUTING.md

@@ -0,0 +1,29 @@
+# Contributing
+
+Use Python 3.10+ and an even-numbered Node.js release >=22.13 (24 LTS recommended).
+The release scripts use Python 3.12. Clone the repository, then create a virtual
+environment. On Windows no activation or execution-policy change is necessary:
+
+```powershell
+py -m venv .venv
+.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
+.\.venv\Scripts\python.exe -m pytest
+```
+
+On macOS/Linux use `python3 -m venv .venv` and `.venv/bin/python` instead.
+
+Keep changes focused and describe their behavior and validation in a pull request.
+Tests mock npm for offline unit checks. Add regression tests for fixes, including
+Windows launcher behavior where relevant. Do not replace the `call "npm.cmd"`
+launcher without testing it on Windows with paths containing spaces.
+
+Before proposing a release, run the checks in [RELEASING.md](RELEASING.md).
+Test a generated default app with `npm ci`, `npm test`, `npm run lint`, and
+`npm run build`; also build a minimal app with all optional tools disabled.
+Never commit generated apps, node_modules, secrets, or virtual environments.
+Update both Python version declarations together when a release requires a bump.
+
+Treat other contributors respectfully. Offer specific, constructive feedback;
+harassment, discrimination, threats, and disclosure of private information are
+not welcome. Maintainers may remove inappropriate content and restrict participation.
+For security concerns, follow [SECURITY.md](SECURITY.md).

belazywithreact-0.1.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 belazywithreact contributors
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
+IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
+DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
+ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER
+DEALINGS IN THE SOFTWARE.

belazywithreact-0.1.0/PKG-INFO

@@ -0,0 +1,205 @@
+Metadata-Version: 2.5
+Name: belazywithreact
+Version: 0.1.0
+Summary: A Python CLI that scaffolds ready-to-use React projects.
+Project-URL: Homepage, https://github.com/Sanju2911/belazywithreact
+Project-URL: Repository, https://github.com/Sanju2911/belazywithreact
+Project-URL: Issues, https://github.com/Sanju2911/belazywithreact/issues
+License-Expression: MIT
+License-File: LICENSE
+Keywords: cli,react,scaffold,typescript,vite
+Classifier: Development Status :: 3 - Alpha
+Classifier: Environment :: Console
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Requires-Python: >=3.10
+Requires-Dist: rich<15.0,>=13.7
+Requires-Dist: typer<1.0,>=0.12
+Provides-Extra: dev
+Requires-Dist: build>=1.2; extra == 'dev'
+Requires-Dist: pytest-cov>=5.0; extra == 'dev'
+Requires-Dist: pytest>=8.0; extra == 'dev'
+Requires-Dist: twine>=6.0; extra == 'dev'
+Description-Content-Type: text/markdown
+
+# belazywithreact
+
+[![CI](https://github.com/Sanju2911/belazywithreact/actions/workflows/tests.yml/badge.svg)](https://github.com/Sanju2911/belazywithreact/actions/workflows/tests.yml)
+
+A Python CLI that creates a React + TypeScript app with Vite and a useful starter
+structure. Version **0.1.0** is the initial release. npm is the supported package
+manager.
+
+## Prerequisites
+
+- Python 3.10 or newer.
+- An even-numbered Node.js release >=22.13; Node.js 24 LTS is recommended.
+- npm on PATH and internet access to download packages from the npm registry.
+
+Check `python --version`, `node --version`, and `npm --version`.
+
+## Installation
+
+Install a published release from PyPI:
+
+```powershell
+python -m pip install belazywithreact
+belazywithreact --help
+```
+
+Install from a local checkout:
+
+```powershell
+python -m pip install .
+```
+
+For development on Windows, a virtual environment avoids global changes and
+does not require changing PowerShell's execution policy:
+
+```powershell
+py -m venv .venv
+.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
+.\.venv\Scripts\belazywithreact.exe --help
+```
+
+On macOS/Linux use `python3 -m venv .venv`, then `.venv/bin/python` and
+`.venv/bin/belazywithreact` instead.
+
+## Usage
+
+```powershell
+belazywithreact create my-app
+cd my-app
+npm run dev
+```
+
+Creation asks for confirmation. `--yes` skips that question and still refuses
+to overwrite an existing destination, including an empty directory.
+
+Defaults include CSS + Tailwind CSS 4, React Router, Axios, Zustand, ESLint,
+Prettier, and Vitest. Tailwind uses its official Vite plugin and CSS import;
+customize its theme in CSS. ESLint is explicitly configured for TypeScript and
+React. `npm test` runs once, and `npm run test:watch` starts watch mode.
+
+A minimal CSS app:
+
+```powershell
+belazywithreact create my-app --styling css --no-router --no-axios --no-zustand --no-eslint --no-prettier --no-vitest --yes
+```
+
+| Option | Default | Behavior |
+| --- | --- | --- |
+| `--styling css\|tailwind\|both` | `both` | Enables Tailwind in tailwind/both; custom starter CSS is always included |
+| `--router` / `--no-router` | enabled | Home and fallback routes with BrowserRouter |
+| `--axios` / `--no-axios` | enabled | Axios API client and public API base URL example |
+| `--zustand` / `--no-zustand` | enabled | Example counter store |
+| `--eslint` / `--no-eslint` | enabled | ESLint config, dependencies, and lint script |
+| `--prettier` / `--no-prettier` | enabled | Format script and ignore file |
+| `--vitest` / `--no-vitest` | enabled | Test scripts and example unit test |
+| `--package-manager npm` | `npm` | Only npm is supported in 0.1.0 |
+| `--yes`, `-y` | disabled | Skip confirmation |
+
+Use `belazywithreact create --help` for all options.
+
+## Generated structure
+
+```text
+my-app/
+  src/
+    assets/
+    components/Button.tsx
+    hooks/
+    layouts/
+    pages/HomePage.tsx
+    services/api.ts          # when Axios is enabled
+    store/useAppStore.ts     # when Zustand is enabled
+    styles/index.css
+    styles/tailwind.css
+    types/
+    utils/example.test.ts    # when Vitest is enabled
+    App.tsx
+    main.tsx
+  .env.example
+  eslint.config.js          # when ESLint is enabled
+  vite.config.ts
+  package.json
+  package-lock.json
+  README.md
+```
+
+The Button supports native button props and children. Customize the generated
+components, folders, API client, and store after creation. Empty starter folders
+contain .gitkeep files. The scaffold does not provide authentication, backend
+services, deployment, or arbitrary folder/component generation flags.
+
+Validate your generated app:
+
+```powershell
+npm ci
+npm test
+npm run lint
+npm run build
+```
+
+Test and lint commands require their respective enabled options.
+BrowserRouter deployments need a server fallback to index.html for route URLs.
+All `VITE_` environment variables are public browser values, never secrets.
+
+## Troubleshooting
+
+- **Missing Node/npm or WinError 2:** install Node.js 24 LTS and reopen the
+  terminal so PATH updates. On Windows, check `where.exe node` and
+  `where.exe npm`; `npm.cmd --version` should work. The CLI preserves its
+  tested `call "<resolved npm.cmd>"` launch method for paths containing spaces.
+- **Unsupported Node version:** upgrade to an even-numbered release >=22.13.
+  The generated tooling needs a newer Node version than some older Vite releases.
+- **Invalid name:** use a directory name starting with a letter or number and
+  containing only letters, numbers, dots, underscores, or hyphens. Names cannot
+  end in a dot, exceed 214 characters, use Windows device names like CON/LPT1,
+  or use npm-reserved names. Path separators and shell operators are rejected.
+  Vite normalizes uppercase directory names to valid npm package names.
+- **Destination exists:** choose another name; existing files are preserved.
+- **npm failure or interruption:** read npm's output and check network/PATH.
+  Partial projects are preserved. Inspect them before manually removing or
+  repairing them; a retry with the same name will refuse to overwrite them.
+- **Dependency advisory:** run `npm audit` and review compatible upgrades;
+  do not blindly force a major upgrade.
+
+## Architecture and development
+
+`cli.py` parses options with Typer and prints progress/errors with Rich.
+`validators.py` validates names, destination boundaries, and Node prerequisites.
+`scaffold.py` invokes create-vite **9.2.1**, writes the starter files, installs
+selected tools, updates package.json, and synchronizes package-lock.json. npm
+output remains visible, and failures return nonzero status. Interruption during
+creation returns 130. The CLI never deletes a partial project automatically.
+
+The Vite creator and optional-tool install requests specify reviewed versions;
+Vite's base template and npm semver ranges can still resolve newer compatible
+dependencies. Commit the generated lockfile and use `npm ci` for reproducible
+app installations. Revalidate dependencies before a future CLI release.
+
+```powershell
+python -m pytest
+python -m build
+python -m twine check --strict dist/*
+python scripts/check_dist.py
+```
+
+Unit tests mock npm and run offline. CI checks Python 3.10, 3.12, and 3.14 on
+Windows, macOS, and Linux, validates distributions, and builds real default and
+minimal React apps. See [CONTRIBUTING.md](CONTRIBUTING.md) for contributions,
+[SECURITY.md](SECURITY.md) for security reporting, and
+[RELEASING.md](RELEASING.md) for TestPyPI-first Trusted Publishing and explicit
+production-release approval. GitHub and both package-index accounts must be
+configured separately before publication.
+
+## License
+
+[MIT](LICENSE).

belazywithreact-0.1.0/README.md

@@ -0,0 +1,175 @@
+# belazywithreact
+
+[![CI](https://github.com/Sanju2911/belazywithreact/actions/workflows/tests.yml/badge.svg)](https://github.com/Sanju2911/belazywithreact/actions/workflows/tests.yml)
+
+A Python CLI that creates a React + TypeScript app with Vite and a useful starter
+structure. Version **0.1.0** is the initial release. npm is the supported package
+manager.
+
+## Prerequisites
+
+- Python 3.10 or newer.
+- An even-numbered Node.js release >=22.13; Node.js 24 LTS is recommended.
+- npm on PATH and internet access to download packages from the npm registry.
+
+Check `python --version`, `node --version`, and `npm --version`.
+
+## Installation
+
+Install a published release from PyPI:
+
+```powershell
+python -m pip install belazywithreact
+belazywithreact --help
+```
+
+Install from a local checkout:
+
+```powershell
+python -m pip install .
+```
+
+For development on Windows, a virtual environment avoids global changes and
+does not require changing PowerShell's execution policy:
+
+```powershell
+py -m venv .venv
+.\.venv\Scripts\python.exe -m pip install -e ".[dev]"
+.\.venv\Scripts\belazywithreact.exe --help
+```
+
+On macOS/Linux use `python3 -m venv .venv`, then `.venv/bin/python` and
+`.venv/bin/belazywithreact` instead.
+
+## Usage
+
+```powershell
+belazywithreact create my-app
+cd my-app
+npm run dev
+```
+
+Creation asks for confirmation. `--yes` skips that question and still refuses
+to overwrite an existing destination, including an empty directory.
+
+Defaults include CSS + Tailwind CSS 4, React Router, Axios, Zustand, ESLint,
+Prettier, and Vitest. Tailwind uses its official Vite plugin and CSS import;
+customize its theme in CSS. ESLint is explicitly configured for TypeScript and
+React. `npm test` runs once, and `npm run test:watch` starts watch mode.
+
+A minimal CSS app:
+
+```powershell
+belazywithreact create my-app --styling css --no-router --no-axios --no-zustand --no-eslint --no-prettier --no-vitest --yes
+```
+
+| Option | Default | Behavior |
+| --- | --- | --- |
+| `--styling css\|tailwind\|both` | `both` | Enables Tailwind in tailwind/both; custom starter CSS is always included |
+| `--router` / `--no-router` | enabled | Home and fallback routes with BrowserRouter |
+| `--axios` / `--no-axios` | enabled | Axios API client and public API base URL example |
+| `--zustand` / `--no-zustand` | enabled | Example counter store |
+| `--eslint` / `--no-eslint` | enabled | ESLint config, dependencies, and lint script |
+| `--prettier` / `--no-prettier` | enabled | Format script and ignore file |
+| `--vitest` / `--no-vitest` | enabled | Test scripts and example unit test |
+| `--package-manager npm` | `npm` | Only npm is supported in 0.1.0 |
+| `--yes`, `-y` | disabled | Skip confirmation |
+
+Use `belazywithreact create --help` for all options.
+
+## Generated structure
+
+```text
+my-app/
+  src/
+    assets/
+    components/Button.tsx
+    hooks/
+    layouts/
+    pages/HomePage.tsx
+    services/api.ts          # when Axios is enabled
+    store/useAppStore.ts     # when Zustand is enabled
+    styles/index.css
+    styles/tailwind.css
+    types/
+    utils/example.test.ts    # when Vitest is enabled
+    App.tsx
+    main.tsx
+  .env.example
+  eslint.config.js          # when ESLint is enabled
+  vite.config.ts
+  package.json
+  package-lock.json
+  README.md
+```
+
+The Button supports native button props and children. Customize the generated
+components, folders, API client, and store after creation. Empty starter folders
+contain .gitkeep files. The scaffold does not provide authentication, backend
+services, deployment, or arbitrary folder/component generation flags.
+
+Validate your generated app:
+
+```powershell
+npm ci
+npm test
+npm run lint
+npm run build
+```
+
+Test and lint commands require their respective enabled options.
+BrowserRouter deployments need a server fallback to index.html for route URLs.
+All `VITE_` environment variables are public browser values, never secrets.
+
+## Troubleshooting
+
+- **Missing Node/npm or WinError 2:** install Node.js 24 LTS and reopen the
+  terminal so PATH updates. On Windows, check `where.exe node` and
+  `where.exe npm`; `npm.cmd --version` should work. The CLI preserves its
+  tested `call "<resolved npm.cmd>"` launch method for paths containing spaces.
+- **Unsupported Node version:** upgrade to an even-numbered release >=22.13.
+  The generated tooling needs a newer Node version than some older Vite releases.
+- **Invalid name:** use a directory name starting with a letter or number and
+  containing only letters, numbers, dots, underscores, or hyphens. Names cannot
+  end in a dot, exceed 214 characters, use Windows device names like CON/LPT1,
+  or use npm-reserved names. Path separators and shell operators are rejected.
+  Vite normalizes uppercase directory names to valid npm package names.
+- **Destination exists:** choose another name; existing files are preserved.
+- **npm failure or interruption:** read npm's output and check network/PATH.
+  Partial projects are preserved. Inspect them before manually removing or
+  repairing them; a retry with the same name will refuse to overwrite them.
+- **Dependency advisory:** run `npm audit` and review compatible upgrades;
+  do not blindly force a major upgrade.
+
+## Architecture and development
+
+`cli.py` parses options with Typer and prints progress/errors with Rich.
+`validators.py` validates names, destination boundaries, and Node prerequisites.
+`scaffold.py` invokes create-vite **9.2.1**, writes the starter files, installs
+selected tools, updates package.json, and synchronizes package-lock.json. npm
+output remains visible, and failures return nonzero status. Interruption during
+creation returns 130. The CLI never deletes a partial project automatically.
+
+The Vite creator and optional-tool install requests specify reviewed versions;
+Vite's base template and npm semver ranges can still resolve newer compatible
+dependencies. Commit the generated lockfile and use `npm ci` for reproducible
+app installations. Revalidate dependencies before a future CLI release.
+
+```powershell
+python -m pytest
+python -m build
+python -m twine check --strict dist/*
+python scripts/check_dist.py
+```
+
+Unit tests mock npm and run offline. CI checks Python 3.10, 3.12, and 3.14 on
+Windows, macOS, and Linux, validates distributions, and builds real default and
+minimal React apps. See [CONTRIBUTING.md](CONTRIBUTING.md) for contributions,
+[SECURITY.md](SECURITY.md) for security reporting, and
+[RELEASING.md](RELEASING.md) for TestPyPI-first Trusted Publishing and explicit
+production-release approval. GitHub and both package-index accounts must be
+configured separately before publication.
+
+## License
+
+[MIT](LICENSE).

belazywithreact-0.1.0/RELEASING.md

@@ -0,0 +1,137 @@
+# Releasing belazywithreact
+
+The first release candidate is **0.1.0**, retaining the existing version.
+No tag or PyPI publication is implied by these instructions. On 2026-10-13,
+the PyPI and TestPyPI JSON endpoints returned 404 for this name. That does not
+guarantee name availability: pending publishers do not reserve names.
+Check again immediately before publishing. Do not replace a project owned by
+someone else or attempt to reuse an already uploaded version/file.
+
+On 2026-10-14, production PyPI's pending publisher was registered with explicit
+approval for configuration only. TestPyPI's publisher was registered and its
+workflow successfully published 0.1.0 from commit 590bfb9; clean-environment
+installation, package origin, dependency checks, and CLI execution were verified.
+Production publication still requires separate explicit approval. The final
+release documentation was updated afterward; the tested CLI source is preserved.
+
+## GitHub setup
+
+The public repository is [Sanju2911/belazywithreact](https://github.com/Sanju2911/belazywithreact),
+created and verified on 2026-10-14.
+Do not initialize a second README, license, or .gitignore remotely. Verify
+`git remote -v` before setting origin and pushing `main`; never force-push.
+Update project URLs in pyproject.toml only after verifying the repository exists.
+Wait for the **CI** workflow to pass, including all three operating systems.
+
+The GitHub environments **testpypi** and **pypi** were created on 2026-10-14.
+The **pypi** environment requires review by **Sanju2911**, disallows administrator
+bypass, and permits only tags matching `v*`. Self-review remains allowed so the
+sole maintainer can approve a release. Verify these protections under Settings >
+Environments before each production release. Environment names in PyPI
+configuration must match the workflow exactly.
+
+The workflow file alone does not create these protections. If they are removed,
+publishing a non-prerelease GitHub Release could start the production upload.
+Do not publish a GitHub Release until the final artifacts have been reviewed and
+the owner has explicitly approved production publication.
+
+## Account and Trusted Publisher setup
+
+Create/access your accounts directly at [PyPI](https://pypi.org/account/register/)
+and [TestPyPI](https://test.pypi.org/account/register/). They are separate services.
+Verify email and complete their required account security setup. Never paste
+passwords, tokens, or recovery codes into chat or repository files.
+
+For a new package, use the account's **Publishing** page to add a pending
+GitHub publisher. For an existing package you own, use its **Publishing** settings.
+Set these fields separately for each service:
+
+| Field | Production PyPI | TestPyPI |
+| --- | --- | --- |
+| PyPI project name | `belazywithreact` | `belazywithreact` |
+| GitHub owner | `Sanju2911` | `Sanju2911` |
+| GitHub repository | `belazywithreact` | `belazywithreact` |
+| Workflow filename | `publish.yml` | `testpypi.yml` |
+| GitHub environment | `pypi` | `testpypi` |
+
+The workflow filename is the basename, not `.github/workflows/publish.yml`.
+OIDC uses `id-token: write` only in the upload job. Build jobs have read-only
+repository access. No API-token secrets are needed. Actions are pinned to
+verified commit SHAs; review and update those pins periodically.
+
+## Local validation
+
+Use Python 3.12 for release scripts, in a development virtual environment:
+
+```powershell
+python -m pip install --upgrade build twine
+python -m pip install -e ".[dev]"
+python -m pytest
+python scripts/check_version.py
+python -m build
+python -m twine check --strict dist/*
+python scripts/check_dist.py
+Get-FileHash dist/* -Algorithm SHA256
+```
+
+Keep dist limited to the current wheel and sdist. Move old artifacts aside before
+building another version. The upload-set checker rejects extra files.
+Check that wheel metadata, README, license and verified project URLs are correct.
+Test the wheel in a new venv, then run `belazywithreact --help` and scaffold an app.
+For the generated default app run `npm ci`, `npm test`, `npm run lint`, and
+`npm run build`. Also build with all optional features disabled.
+
+## TestPyPI first
+
+After configuring its publisher and environment and authorizing a test upload,
+run GitHub Actions > **Publish to TestPyPI** > **Run workflow**, selecting the
+reviewed branch/ref. This manual workflow never publishes to production.
+Check the upload job result and inspect the actual TestPyPI package page.
+
+Use a clean environment to verify that the artifact comes from TestPyPI:
+
+```powershell
+py -m venv .testpypi-venv
+.\.testpypi-venv\Scripts\python.exe -m pip install --index-url https://test.pypi.org/simple/ --no-deps belazywithreact==0.1.0
+.\.testpypi-venv\Scripts\python.exe -m pip install --index-url https://pypi.org/simple/ "typer>=0.12,<1" "rich>=13.7,<15"
+.\.testpypi-venv\Scripts\python.exe -m pip check
+.\.testpypi-venv\Scripts\belazywithreact.exe --help
+```
+
+Then scaffold and validate an app. Installing the package without dependencies
+first ensures its origin; dependencies are obtained separately from normal PyPI.
+The conventional alternative is `--index-url https://test.pypi.org/simple/
+--extra-index-url https://pypi.org/simple/`, but pip combines indexes without
+prioritizing the primary one. Confirm the downloaded artifact's source if using it.
+
+## First production release
+
+Show the owner: version **0.1.0**, the two filenames
+`belazywithreact-0.1.0-py3-none-any.whl` and `belazywithreact-0.1.0.tar.gz`,
+their SHA256 hashes, local validation, successful CI, and TestPyPI verification.
+Obtain explicit approval for the exact action: create tag `v0.1.0` at the reviewed
+commit and publish a non-prerelease GitHub Release for that tag, triggering
+`publish.yml`; then approve the protected **pypi** environment upload job.
+Do not perform this action merely because the repository is ready.
+
+The production workflow tests, verifies tag/version consistency, builds, checks,
+and transfers only those two distributions to a separate publishing job.
+Prereleases are ignored. After upload, verify the actual PyPI project page and
+install `belazywithreact==0.1.0` from normal PyPI in a clean environment. An
+existing workflow or green build is not evidence of successful publication.
+
+## Future versions
+
+Update `project.version` in pyproject.toml and `__version__` in
+src/belazywithreact/__init__.py together. Document the changes, repeat validation,
+commit and push, wait for CI, publish to TestPyPI, and obtain production approval.
+Create a matching `v<version>` release tag only after approval. Never overwrite
+or re-upload an existing release's files; fixes require a new version.
+
+Official references:
+
+- [PyPI pending publishers](https://docs.pypi.org/trusted-publishers/creating-a-project-through-oidc/)
+- [PyPI OIDC publishing and TestPyPI endpoint](https://docs.pypi.org/trusted-publishers/using-a-publisher/)
+- [Python Packaging workflow guide](https://packaging.python.org/en/latest/guides/publishing-package-distribution-releases-using-github-actions-ci-cd-workflows/)
+- [GitHub environment protection](https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/manage-environments)
+- [Official PyPA publishing action](https://github.com/pypa/gh-action-pypi-publish)

belazywithreact-0.1.0/SECURITY.md

@@ -0,0 +1,16 @@
+# Security
+
+This initial release does not promise long-term support. Security fixes should
+be applied by upgrading to a maintained release when one is available.
+
+Do not include credentials, tokens, `.env` values, or personal data in public
+issues. Private vulnerability reporting is enabled: use GitHub's
+**Report a vulnerability** feature under the repository's Security tab.
+If that feature becomes unavailable, request a private contact channel without
+disclosing exploit details in public.
+
+The CLI downloads and runs create-vite and npm packages from the npm registry.
+Review generated package.json and package-lock.json before deployment, and run
+`npm audit` to check the generated project's dependencies. The CLI does not
+disable npm security checks. All `VITE_` environment variables are exposed to
+the browser; never place secrets in them.

belazywithreact-0.1.0/pyproject.toml

@@ -0,0 +1,46 @@
+[build-system]
+requires = ["hatchling>=1.27,<2"]
+build-backend = "hatchling.build"
+
+[project]
+name = "belazywithreact"
+version = "0.1.0"
+description = "A Python CLI that scaffolds ready-to-use React projects."
+readme = "README.md"
+requires-python = ">=3.10"
+license = "MIT"
+license-files = ["LICENSE"]
+keywords = ["react", "vite", "typescript", "scaffold", "cli"]
+classifiers = [
+  "Development Status :: 3 - Alpha",
+  "Environment :: Console",
+  "Operating System :: OS Independent",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3 :: Only",
+  "Programming Language :: Python :: 3.10",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Programming Language :: Python :: 3.14",
+]
+dependencies = ["typer>=0.12,<1.0", "rich>=13.7,<15.0"]
+
+[project.urls]
+Homepage = "https://github.com/Sanju2911/belazywithreact"
+Repository = "https://github.com/Sanju2911/belazywithreact"
+Issues = "https://github.com/Sanju2911/belazywithreact/issues"
+
+[project.optional-dependencies]
+dev = ["pytest>=8.0", "pytest-cov>=5.0", "build>=1.2", "twine>=6.0"]
+
+[project.scripts]
+belazywithreact = "belazywithreact.cli:app"
+
+[tool.hatch.build.targets.wheel]
+packages = ["src/belazywithreact"]
+
+[tool.hatch.build.targets.sdist]
+include = ["/src", "/tests", "/scripts", "/pyproject.toml", "/README.md", "/LICENSE", "/CONTRIBUTING.md", "/RELEASING.md", "/SECURITY.md"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]