Issue: Non-standard install of Node cannot be found when running SSG scripts

[wale]

Describe the bug
When initialising a project with FrontMatterCMS & Astro, alongside a non-standard version manager (in my case, mise), it throws an error and proceeds to not find content collections.

To Reproduce
Steps to reproduce the behavior:
(requires using a mise (or nvm) installed node or otherwise)

1. Go to the side bar and click the FrontMatterCMS button.
2. Click on 'Initialize Project'
3. Scroll down to 'Create Content Types for your Astro Content Collections'.
4. 'No Astro Content Collections found'.

Expected behavior
Astro content collections being detected and the script running successfully.

Screenshots
If applicable, add screenshots to help explain your problem.

Device: Fedora Linux 40 x86_64, kernel 6.10.9-200.fc40.x86_64, fish-shell 3.7.0

• OS: Linux
• Front Matter CMS Version: tested on beta v10.5.110679225, stable v10.4.1
• Browser: N/A

Additional context
It's possible that this is caused by FrontMatterCMS not having an option to pass a Node binary for its SSG scripts, and calls node based on a shell discovered by VSCode.

vscode-front-matter/src/listeners/dashboard/SsgListener.ts

Line 173 in 788d024

const fullScript = `node "${tempScriptPath.fsPath}" "${contentConfigFile.fsPath}"`;

[estruyf]

@wale, your observations are correct. There is currently no option for specifying the Node binary location, only for the custom actions/scripts, but on initialization, it tries to use the general node command.

[estruyf]

@wale I have implemented a change into the latest beta where it first tries to resolve the node executable path. This is related to the #882 issue.