adam/vscode-front-matter
1
0 Fork 0
mirror of https://github.com/estruyf/vscode-front-matter.git synced 2026-11-03 09:02:19 +01:00
Code Issues 77 Packages Projects Releases Wiki Activity

Enhancement: Run Server in nix develop #730

New Issue
Open
opened 2026-10-05 03:02:39 +02:00 by adam · 1 comment
adam commented 2026-10-05 03:02:39 +02:00
Owner
Copy link
Copy source

Is your feature request related to a problem? Please describe.

When working in a Nix-based development environment (nix develop), Frontmatter CMS’s built-in server functionality does not appear to inherit the shell environment. As a result, attempting to launch the development server via the extension UI fails or behaves inconsistently. This breaks the expected development workflow for projects using Nix for reproducibility and dependency management.

Describe the solution you'd like

I’d like Frontmatter CMS to recognize and integrate with the nix develop shell context when running the dev server. This could be implemented in one of the following ways:

  • Provide an option to specify a custom command or shell context for server start
  • Detect whether the workspace is inside a Nix shell and spawn processes accordingly
  • Allow configuration to disable internal server start and delegate to external terminal-based commands, with status integration if possible

This would make the CMS more compatible with reproducible development environments and declarative tooling setups.

Describe alternatives you've considered

  • Manually running npm run start (or equivalent) in a terminal that’s already inside a nix develop shell. This works but disconnects the CMS UI from the server process.
  • Overriding shell environments in the extension or editor, which introduces brittleness and doesn't generalize well across systems or team workflows.

Additional context

Nix-based setups are increasingly common in projects that prioritize reproducibility and environment isolation. Seamless support for nix develop workflows would reduce friction for developers working in these ecosystems and align Frontmatter CMS more closely with declarative infrastructure paradigms.

**Is your feature request related to a problem? Please describe.** When working in a Nix-based development environment (`nix develop`), Frontmatter CMS’s built-in server functionality does not appear to inherit the shell environment. As a result, attempting to launch the development server via the extension UI fails or behaves inconsistently. This breaks the expected development workflow for projects using Nix for reproducibility and dependency management. **Describe the solution you'd like** I’d like Frontmatter CMS to recognize and integrate with the `nix develop` shell context when running the dev server. This could be implemented in one of the following ways: - Provide an option to specify a custom command or shell context for server start - Detect whether the workspace is inside a Nix shell and spawn processes accordingly - Allow configuration to disable internal server start and delegate to external terminal-based commands, with status integration if possible This would make the CMS more compatible with reproducible development environments and declarative tooling setups. **Describe alternatives you've considered** - Manually running `npm run start` (or equivalent) in a terminal that’s already inside a `nix develop` shell. This works but disconnects the CMS UI from the server process. - Overriding shell environments in the extension or editor, which introduces brittleness and doesn't generalize well across systems or team workflows. **Additional context** Nix-based setups are increasingly common in projects that prioritize reproducibility and environment isolation. Seamless support for `nix develop` workflows would reduce friction for developers working in these ecosystems and align Frontmatter CMS more closely with declarative infrastructure paradigms. <!-- github-sync-id:2962130212 -->
adam commented 2026-10-05 03:02:40 +02:00
Author
Owner
Copy link
Copy source

Nix is indeed not part of the predefined list, but you are able to configure the start command with the following setting: frontMatter.framework.startCommand. Once set, you should be able to start the local server from the FM Actions panel.

Nix is indeed not part of the predefined list, but you are able to configure the start command with the following setting: `frontMatter.framework.startCommand`. Once set, you should be able to start the local server from the FM Actions panel. <!-- github-comment-id:2783027854 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/vscode-front-matter#730