`static:generate` does not warn about the Vite development server running

[a-kla]

Tempest version

2.14

PHP version

8.4

Operating system

Linux

Description

Edit 2: Updated Description for more clarity.

I had Vite + Plugin installed as described in the Tempest Doc.
I tried to build a static Page:

$ ./tempest static:generate --crawl

// GENERATING STATIC PAGES
/ .............................................................................................................. 3 DEAD LINKS
Failures .................................................................................................................. 1
Static pages generated .................................................................................................... 0

// DEAD LINKS
/ ......................................................................................................................... #
/ ......................................................................................................................... #
/ ......................................................................................................................... #

TL;DR: This behavior occurs only when a node Server is running in the background (npm dev) at the same time.

Without --crawl it generates the page but the index.html includes:

<script type="module" src="http://[::]:5173/@vite/client"></script>
<script type="module" src="http://[::]:5173/src/main.entrypoint.ts"></script>
<link rel="stylesheet" href="http://[::]:5173/src/main.entrypoint.css" />

Later the same command worked as expected:

<script type="module" src="assets/main.entrypoint-BY3IQ6qW.js" />
<link rel="stylesheet" href="assets/main-BmsNWnvI.css" />

But then i got the "DEAD LINKS" again and did not see why.

Now I know: If Node is running in the background ( pnpm dev / npm run dev) this happens.
And sometimes it don't start to work again after stooping Node. Even restarting my PC and deleting .tempest/ did not help.

A minimal repository for reproduction
The last commit shows the difference between running pnpm dev and not running it.

But I don't need Vite atm and removed it.

[innocenzi]

Hey, would you mind providing a reproduction? A minimal repository would be nice.

[a-kla]

WIP, but strangely the minimal example works.

I don't have a clue what breaks it.
I use the same

• dev container
• .env
• vite.config.js
• package.json
• composer.json (almost, just use pest)

[a-kla]

Found it!

If I run the node server (pnpm dev) ./tempest static:generate will use it.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[xHeaven]

What would be the desired behavior here? If you run static:generate while your dev server is running, and you haven't run build yet since you last edited your files, you will have a stale generation, won't you? Should we explicitly disallow static:generate when the dev server is running, or should we implicitly run build for you?

[innocenzi]

That's a good option @xHeaven, yeah! There are other potential confusions points, though, such as running static generation on a stale local build. Not sure if we should go down this rabbit hole, but checking if the development server is running is at least a quick win.

[a-kla]

should we implicitly run build for you?

No, ./tempest static:generate works perfect if node is not running.

I did not expect that running NodeJs has any side effect on my PHP tools, in particular ./tempest static:generate.
I did not found anything about it in the Doc and wasted a lot of time to find it out.

…checking if the development server is running is at least a quick win.

There is already anywhere a IMHO gratuitously check, that's the issue.
I don't know why it is there.

In my eyes it is a bug since i want a static site, no matter if node is running or not.
If some one know about this behavior, he can stop Node (or may not).

So the options are

• just doc it
• let the command warn that it detected Node and chose to relay on it.
• remove this "feature"