Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info

    async *__getField() {

    SyntaxError: Unexpected token *
    at createScript (vm.js:80:10)
    at Object.runInThisContext (vm.js:139:10)
    at Module._compile (module.js:607:28)
    at Object.Module._extensions..js (module.js:654:10)
    at Module.load (module.js:556:32)
    at tryModuleLoad (module.js:499:12)
    at Function.Module._load (module.js:491:3)
    at Module.require (module.js:587:17)
    at require (internal/module.js:11:18)
    at Object.<anonymous> (/home/eagle/.nvm/versions/node/v8.9.4/lib/node_modules/composer-rest-server/node_modules/@tim-lai/isomorphic-form-data/lib/index.js:2:18)

    @cbj4074 no problem is resolved for me .

    i have an application with an "api" module. i want to separate the api out into its own repo.

    however, I have a problem with the relationship with the app package:

    • in terms of installation, the app is the parent package, and the api provides an api implementation.
    • in terms of logical dependency, the api uses all of the business logic from the app - the api is the parent package, and the app is a dependency.

    how can composer organize/express this?

    Ben Johnson

    @adrian-enspired I'm not sure what you mean, exactly, by "how can composer organize/express this?"

    If I understand the essence of your question, though, you're asking how to define the relationship between the packages.

    On its face, it seems as simple as making the app package a dependency of the api package.

    In the api package's composer.json:

    "require": {
        "app": "dev-master",
    yes; this would be the correct relationship code-wise. the issue is that "api" is not the package that is installed - "app" is. that is, it's composer install app, not composer install api. api cannot be the parent/installable package, as "app" must exist on its own. there are other frontends that use it.
    the other frontends would have this same issue, save for the fact they're not written in php (and so don't use composer)
    the only composer solution i can imagine is a dummy package of some sort, which would be extremely difficult (and likely unreliable) to produce/maintain
    re: "installed app": i can't simply make "app" a dependency of "api" and then install "api" instead. it makes no sense perform app updates as a side-effect of updating the api.
    trying to explain things more clearly - logically, they should be separate installs. but doing so would leave api's dependency on app unclear/unexpressed.
    Tim Nolte
    @adrian-enspired to me it sounds like you haven't really separated out the code well enough to make clear package dependencies. Does your app use the API or serve the API? If your app uses the API then the business logic should be in the API and the API should be a standalone service. If the app doesn't use the API then I would say your business logic should be it's own package as a dependency library. The API should still be a service and then can also have the business logic as a dependency.

    the app is the business logic. the api serves it (but is not the only code that does so - e.g., we have a cli frontend, legacy web controllers, and so forth). so in dependency terms, the app is a dependency of the api.

    logically, however, the app is not a component of the api. the goal is to make them into two separate packages. the api depends on the app existing, but cannot require and install it as composer would a normal dependency.


    Hi there.

    I have composer upgrade and it tells me this:
    Remove clarkwinkelmann/flarum-ext-group-invitation (0.1.1) In Filesystem.php line 217: Could not deleted /vendor/clarkwinkelmann/flarum-ext-group-invitation/src/Access/InvitationPolicy.php

    and I have composer require fof/socialprofile and it tells me this ./composer.json is not writable

    I have ofcourse VPS, 755, user/group=www-data/www-data
    What happens ? :S

    Ben Johnson
    @Carine933_twitter As which user are you executing the composer ... command?
    (i.e., what is the output of the whoami command)
    Does any one knows, if I upgrade illuminate/database dependency from 5.2.45 to the latest 8.x, what should I do? Is there an upgrade guide there?
    Ben Johnson
    @Carine933_twitter My best guess is that PHP is running as a user in the www-data group, but not the www-data user, in which case, 755 is, in effect, read-only. You should try to determine as whom PHP is executing.
    @phoenixg I'm not sure that's possible without upgrading laravel/framework altogether.
    Hello. Is there a way for composer to execute a post install script (after composer install finishes) ?
    2 replies
    I'm looking for something similar to npm's postinstall script
    Hi, does anyone know why I am not able to redirect composer output
        "scripts": {
            "print": "echo Hello World"
    $ composer print &>/dev/null
    Hello World
    it is now working as expected after upgrading from 2.0.2 to 2.0.7 :)
    hello, pls does anybody know what means this strange message?
    php-amqplib/php-amqplib v3.0.0 conflicts with php-amqplib/php-amqplib v3.0.0.
    composer version 2.1.8
    Narinder Singh
    Thomas Ploch
    Hi, I am having a hard time fighting with the opcache preloader and the classmap generated by composer. Some of the classes found in the loader's classmap are not registered in the opcache, in my case Ramsey\Uuid\Uuid, and I don't have a clue why this is the case.