Skip to main content

Development, Scripts & Queues

Select a project on the Projects page to open its controls. Development, scripts, and queues are available according to the project's files and configuration; a recognized JavaScript framework is not required.

Project panel with development, Laravel queue controls, package scripts, and a custom command

Run package scripts​

Project scripts reads the actual scripts entries from package.json. Select a script, check the command preview, and choose Run in terminal. For example, a project declaring dev, watch, and build offers those three scripts. LaraEnv does not add scripts that are absent from the file.

The command uses the detected package manager: npm, pnpm, Yarn, or Bun. Refresh scripts reloads the file after changes. A read or JSON error has a retry action; a project without scripts can still run a custom command.

Scripts open in a new project terminal, using the project's directory, resolved PHP and Node runtimes, and preferred shell. Follow the output there; use Ctrl+C to stop a script such as watch. A build task runs without appended Dev-server port arguments.

Run a custom command​

Enter a command in Custom command and choose Run command, for example:

npm run build -- --watch

This runs the text you entered in the project's terminal. It also works when there is no package.json. Running a command does not change the project's terminal preference or saved Dev command.

Managed Dev server​

Development offers Start Dev, Stop Dev, Logs, and Configure command for projects with package.json, a detected framework, or a configured Dev command. Laravel projects keep their queue controls even without JavaScript tooling.

Without a custom Dev command, LaraEnv uses the project's detected package manager and selects the dev script, falling back to start. If neither script exists, define one or configure a Dev command. Compatible server tools can receive the chosen port; arbitrary script wrappers are not given a forced --port argument.

Use Configure command while the server is stopped to save a project command. It takes precedence over the global Dev command. A custom command runs as written, with {port} replaced by the selected port when present, for example:

php artisan serve --port={port}

The managed Dev server keeps running in the background and has its own live logs. Configure a project proxy port to forward its .test domain to localhost:<port>. The port must match the server's listening port. See Project configuration.

Laravel queue worker​

Laravel projects have a dedicated Queue worker control in Development, including projects without package.json or a recognized JavaScript framework. It manages php artisan queue:work with the resolved project PHP.

  • Start queue / Stop queue controls the background worker.
  • The menu offers Restart while it is running.
  • Start with parameters accepts arguments such as --queue=high,default --tries=3 --timeout=60 while the worker is stopped.

Arguments are remembered per project and reused on the next start. Queue processes are separate from the managed Dev server and terminal scripts.

For scheduled artisan tasks such as schedule:run, use Cron tasks.