I am working on a Laravel package that contains a code editor, terminal, and many more development tools. It allows you to put it behind any route you specify (ex - yoursite.com/dev) through it's configuration file.
Would you even consider using such a package? If so, what features would you like to see implemented?
Emil Moe
Senior Data Engineer
I wouldn't like to mash my editor into the project, those things should be separated. It also raises security risks to my head when I see such things.
A dedicated Laravel editor is on the other hand a great idea. But you have a lot work in front of you to fit in all the features PHPStorm has, so I don't know if it's worth the work. At least if you want to profit from your thousands of hours work it will take, it should be working as an application.
I could see the benefit from an editor that doesn't force me to, but try gently to do best practices in Laravel. This could however also just be a sort of testing environment rather than an editor.
To answer your questions: The security issues are too high for me to ever use such thing.