Code Monkey home page Code Monkey logo

Comments (5)

naderman avatar naderman commented on June 9, 2024

My only concern is that this encourages non-standard setups too much.

from installers.

Seldaek avatar Seldaek commented on June 9, 2024

I agree, I think in most cases it's just misguided, but I am also tired of arguing with people that they shouldn't do it and why, so I am not sure what the best approach is.

from installers.

nicolasblackburn avatar nicolasblackburn commented on June 9, 2024

Well, I'm thinking about using Composer to manage all website dependencies, not only php: js, css. That would be nice for js and css dependencies for example, to be able to distribute in a js or css directory. Sure I could write a custom installer, but it would be more simple just to be able to specify a target dir.

The problem I see with writing a custom installer however is that I don't want to create a composer installer for every imaginable dependency types that I want to include. Also I want to avoid using multiple package managers: I like Composer, I know how to use it, I want to stick with it.

I think adding this target dir feature would help using Composer as a general dependency manager not only tied to php.

from installers.

shama avatar shama commented on June 9, 2024

@nicolasblackburn Why can't you load css and js from the vendor folder?

FWIW, in Node.js we're forced to a single folder node_modules and no custom installers. It seems harsh but actually solves a huge list of problems. One being having a designated folder specifically for dependencies. You can upgrade, downgrade, create or destroy without much thought. If your dependencies are scattered throughout your app it becomes fragile. Upgrading and downgrading could mean destroying non-dependency code and a lot of thought stepping around your installed packages.

from installers.

nicolasblackburn avatar nicolasblackburn commented on June 9, 2024

@shama, I could certainly do this. That's actually what I do and I see good advantages to it too. It is just that it is not common practice to store js and css that way. Lots of front end developers for example use boilerplate or html templates and frameworks where js and css are commonly stored in a js and css directory. It would be nice that Composer be flexible enough to accomodate any website structure.

from installers.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.