Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/luigitemu/pikante-landing/llms.txt

Use this file to discover all available pages before exploring further.

Pikanté Landing is built with Astro 6 and TypeScript. The local development experience is fast and zero-config — Astro’s dev server starts in under a second and hot-reloads components as you edit them. This guide walks you through everything needed to go from a fresh machine to a running local environment.

​
Prerequisites

Before cloning the project, make sure your machine meets the following requirements:
RequirementMinimum versionCheck
Node.js>= 22.12.0node --version
npmbundled with Nodenpm --version
The project’s package.json declares the engine requirement explicitly:
package.json
{
  "engines": {
    "node": ">=22.12.0"
  }
}
If node --version returns a version older than 22.12.0, upgrade via nvm or the official Node.js installer before continuing.

​
Setup

1
Clone the repository
2
git clone <url-del-repo>
4
cd pikante-landing
5
Install dependencies
6
npm install
7
This installs Astro, the React integration, Tailwind CSS v4, Lucide icons, and all other packages listed in package.json.
8
Start the development server
9
npm run dev
10
Astro will print a local URL once the server is ready:
11
🚀  astro  v6.x.x started in Xms

┃ Local    http://localhost:4321/
┃ Network  use --host to expose
12
Open http://localhost:4321 in your browser to see the Pikanté landing page.

​
Available npm scripts

All commands are run from the project root:
ScriptUnderlying commandWhat it does
npm run devastro devStarts the dev server at localhost:4321 with Hot Module Replacement
npm run buildastro buildCompiles a production-ready static site into ./dist/
npm run previewastro previewServes the ./dist/ build locally to verify it before deploying
npm run astroastroRuns any Astro CLI command (e.g. npm run astro -- --help)

​
Hot Module Replacement (HMR)

Astro’s dev server ships with HMR out of the box. When you save a .astro, .css, or TypeScript file, the browser reflects the change immediately — no manual refresh required, and without losing scroll position or component state. This applies to:
  • Component files (src/components/*.astro) — template and prop changes reload only the affected component
  • Global CSS (src/styles/global.css) — style changes are injected without a full page reload
  • Page files (src/pages/*.astro) — layout or import changes trigger a fast page update

​
TypeScript

The project’s tsconfig.json extends Astro’s strict preset, which enables strict null checks, noImplicitAny, and other safety rules. Any TypeScript error in a component frontmatter or script block will surface in the terminal alongside the dev server output — no separate tsc run needed.
Astro component files (.astro) support TypeScript directly inside the frontmatter — the --- fenced block at the top of each file. All imports, props, and local logic in that block are fully type-checked, just like a regular .ts file.

​
VS Code extension

The project includes a .vscode/extensions.json recommendation that VS Code will surface automatically when you open the workspace:
.vscode/extensions.json
{
  "recommendations": ["astro-build.astro-vscode"],
  "unwantedRecommendations": []
}
The Astro extension (astro-build.astro-vscode) provides syntax highlighting, IntelliSense, and inline TypeScript diagnostics for .astro files. When you open the project, VS Code will prompt you to install it. You can also install it manually from the VS Code Marketplace.

Build docs developers (and LLMs) love

Get started for freeTalk to us