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)
Go to the side bar and click the FrontMatterCMS button.
Click on 'Initialize Project'
Scroll down to 'Create Content Types for your Astro Content Collections'.
'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.
**Describe the bug**
When initialising a project with FrontMatterCMS & Astro, alongside a non-standard version manager (in my case, [`mise`](https://mise.jdx.dev/)), 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.
https://github.com/estruyf/vscode-front-matter/blob/788d0241fdf991418d1ad5d42c62f09d14168ca0/src/listeners/dashboard/SsgListener.ts#L173
<!-- github-sync-id:2567691452 -->
@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.
@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.
<!-- github-comment-id:2394967959 -->
@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.
@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.
<!-- github-comment-id:2441705229 -->
Closing this as a stale issue, as there hasn't been any activity on it for a long time. If this is still a problem with the latest version of Front Matter CMS, feel free to reopen it (or create a new issue) and we'll take another look. Thanks!
Closing this as a stale issue, as there hasn't been any activity on it for a long time. If this is still a problem with the latest version of Front Matter CMS, feel free to reopen it (or create a new issue) and we'll take another look. Thanks!
<!-- github-comment-id:6438499936 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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(ornvm) installednodeor otherwise)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.0v10.5.110679225, stablev10.4.1Additional 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
nodebased on a shell discovered by VSCode.https://github.com/estruyf/vscode-front-matter/blob/788d0241fdf991418d1ad5d42c62f09d14168ca0/src/listeners/dashboard/SsgListener.ts#L173
@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.
@wale I have implemented a change into the latest beta where it first tries to resolve the
nodeexecutable path. This is related to the #882 issue.Closing this as a stale issue, as there hasn't been any activity on it for a long time. If this is still a problem with the latest version of Front Matter CMS, feel free to reopen it (or create a new issue) and we'll take another look. Thanks!