composer.json after installed dependencies

[kicaj]

I try understood something...

When I run commands:
composer install --no-dev --optimize-autoloader
composer dump-autoload --optimize
it creating auto load maps for namespaces.

Then I would like remove composer.json file (on production server for security reasons), but the app still required this file.

Why?

[noefleury]

Just tried now and my app can run without any issue without composer.* files.

What error are you getting ?

Cannot reproduce the issue, can you reproduce with a clean Laravel install ?

[kicaj]

When I remove or rename composer.json, I got:

    "message": "file_get_contents(/var/www/html/composer.json): Failed to open stream: No such file or directory",
    "exception": "ErrorException",
    "file": "/var/www/html/vendor/laravel/framework/src/Illuminate/Foundation/Application.php",
    "line": 1707,
    "trace": [...]

[noefleury]

Looks like it's called within the following method :

framework/src/Illuminate/Foundation/Application.php

Line 1700 in 8dfc3d4

public function getNamespace()

So it's linked to some method trying to get your namespace. You should check more precisely your stack-trace.

Or you have two main options :

• override this method and probably use it inside bootstrap/app.php instead of the original Application class
• keep your composer.json in place (it shouldn't be a security issue if your server and website are correctly configured)

[kicaj]

In stack, there are just Laravel's files.

[noefleury]

But there are too many things which could ask for your namespace and without full stack-trace it's impossible to know what is causing this behaviour.