Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Custom "installer-paths" for custom repositories #2293

Closed
AntonShevchuk opened this issue Sep 26, 2013 · 5 comments
Closed

Custom "installer-paths" for custom repositories #2293

AntonShevchuk opened this issue Sep 26, 2013 · 5 comments

Comments

@AntonShevchuk
Copy link

Hi,
I want to install some version of jQuery to custom vendor directory:

{
    "repositories": [
        {
            "type": "package",
            "package": {
                "name": "gemini/jquery",
                "version": "dev-master",
                "dist": {
                    "url": "http://code.jquery.com/jquery-1.10.2.js",
                    "type": "file"
                },
                "require": {
                    "composer/installers": "~1.0"
                }
            }
        }
    ],
    "extra": {
        "installer-paths": {
            "public/js/vendor/{$name}": ["gemini/jquery"]
        }
    }
}

In result, directory /vendor/gemini/jquery and file jquery-1.10.2.js was created, but not moved to public/js/vendor

@Seldaek
Copy link
Member

Seldaek commented Sep 26, 2013

You need a custom package type that would be handled by composer/installers for this, but I don't think there is a generic type. Maybe someone else can help you with this, we don't really support js packages in composer itself.

@Seldaek Seldaek closed this as completed Sep 26, 2013
@AntonShevchuk
Copy link
Author

Yes, bower is prefered for works with js, but why installer-paths won't works?

@stof
Copy link
Contributor

stof commented Sep 26, 2013

installer-paths is a setting used by the composer/installers plugin. So it is used only when the package type is one of the types handled by the plugin. the default type package is not

@Seldaek
Copy link
Member

Seldaek commented Sep 26, 2013

Because it's specific to composer/installers, and it doesn't handle
packages of the default type, so it doesn't apply this.

@AntonShevchuk
Copy link
Author

Thx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants