netlify.toml

# Netlify configuration for gerillass.com.
#
# In the repository rather than the dashboard on purpose. The settings used to
# live only in the Netlify UI, which meant the one that mattered most --
# NODE_VERSION pinned to 14, because create-react-app 3 could not build on
# anything newer -- was invisible to anyone reading the code, and stayed put
# for years after the reason for it was gone.
#
# Netlify only reads a netlify.toml at the repository root. There is another
# one at site/public/netlify.toml which is therefore inert; it is commented out
# in full and kept only for the cache headers somebody drafted there.

[build]
  # The library lives at the root and the site lives in site/, so the build runs
  # from there and installs site/package.json rather than the library's.
  base = "site"
  command = "npm run build"

  # Relative to `base`, which is what Netlify does with paths in this file.
  # Confirmed on the first deploy from this repository rather than assumed.
  publish = "dist"

[build.environment]
  # Vite needs 18 or newer. This is the only place the version is set: the
  # dashboard variable that pinned it to 14 has been deleted, so there is one
  # answer rather than two. `.nvmrc` at the repository root is for people, not
  # for Netlify: with a base directory set, Netlify looks for it in site/.
  NODE_VERSION = "22"

# Three dashboard variables were deleted when this landed, and the site now has
# none at all:
#
#   NETLIFY_USE_YARN               the site is on npm, and its lockfile is
#                                  package-lock.json
#   NETLIFY_PRERENDER_ENABLED      Netlify's prerendering service, with its auth
#     and its auth token           token. It served crawlers a rendered copy of
#                                  what was then a client-rendered app, which is
#                                  how the site kept its search and social
#                                  previews. Every route is generated at build
#                                  time now, so there was nothing left for it to
#                                  do, and Netlify has deprecated it.


# Response headers are in site/public/_headers, not here. They were written
# here first and never reached production: the build has a base directory, and
# the [[headers]] blocks in this file were silently ignored -- verified against
# the live site, which answered with Netlify's defaults on every path. The
# publish directory is what Netlify reads for this, the same as _redirects.