Chore: remove memory test from CI

[bholmesdev]

Changes

Remove our memory smoke test from CI only (test still present and manually runnable)

Why?

• after speaking with @natemoo-re, it sounds like this memory test addressed out-of-date concerns for the compiler
• this test causes issues with Vite 3, which relies on resolving the astro package to force-optimize dependencies. Since this test imports and calls the dev command directly (rather than using execa), Vite fails to resolve astro as an installed dependency. We can refactor this test to use execa instead if we feel this test is necessary!

Testing

Remove mk.js + command call from the CI

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: db8802c

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
astro-scripts	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[FredKSchott]

If it’s not bothering anyone, can we leave the script in the repo? I remember this randomly being useful a couple of times when I was tracking down perf issues.

[bholmesdev]

@FredKSchott This test is breaking Vite 3 (see PR comments) but maybe we can refactor to use execa instead? I'm not sure if that breaks the spirit of these tests

[FredKSchott]

It’s not just a test! You can run the script yourself and it starts in a “watch” mode.

To be super clear, +1000 on removing from CI. But would love to keep the script for personal/maintainer use

[bholmesdev]

@FredKSchott Ah gotcha! Removing from the CI would be perfect, yes 👍

[bholmesdev]

Update: looks like manually running outside the CI also breaks with Vite 3... experimenting with a refactor to use execa instead

Second update: Vite might be removing this hard bomb from Vite 3. Logged an issue for discussion. Removing this test from our CI for now though since y'all agree!