Try "laravel new"

Open
#61 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
laravel, shell
Domain
cli, tooling

Research direction

No file or test is named; start by reading the existing try command entry point and how it handles the configured tries directory and command arguments. Compare that flow with the requested laravel new sequence, including prompting for a dated directory name, letting Laravel create it, and entering the resulting project; done means this works for Laravel and similar directory-creating CLI tools.

Written by the indexing model from the issue text.

Description

Hello,

Thank you for the fantastic work on this, I love it.

Just one thing, sometimes I like to experiment with Laravel, but Laravel's installer makes its own directory:

$ laravel new test

The above command makes a new test directory in the current working directory.

It would be amazing if try could handle this scenario, something like try laravel new that would get the directory name ready (don't create the directory, as Laravel creates it) and then run laravel new $directory.

It would essentally need to do this:

  1. Ask for the name of the new directory, dated: e.g. 2025-11-25-test
  2. cd into the configured tries directory: e.g. cd ~/src/tries
  3. Pass the directory name through to the command line tool: e.g. laravel new 2025-11-25-test
  4. cd into the newly installed Laravel project: cd ~/src/tries/2025-11-25-test

I'm using Laravel's installer as an example here, but this could theoretically work with any command line tool which creates its own directory. Great for one-line commands that install frameworks or starter kits for projects!

Dominant language
Shell
Stars
4k
Forks
159
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tobi/try

All issues in tobi/try

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.