What Justin Wood said: this definitely does not belong in Elixir *core*. This is a mailing list about the Elixir language and standard library.
*José Valim* www.plataformatec.com.br Skype: jv.ptec Founder and Director of R&D On Thu, Jun 8, 2017 at 12:43 AM, Justin Wood <[email protected]> wrote: > I think this functionality would be good for a third party library. Not > all Elixir applications would have use for something like this. > > On Jun 7, 2017 6:41 PM, "Aleksandr Pavliutin" < > [email protected]> wrote: > >> It would be great, if I can manage node deps with mix. >> >> As I understand, logic same as for hex repo: >> - fetch need files from repo(github) using package.json config instead >> mix.exs, package.exs or rebar.config; >> - fetch dependencies for package using MIX_ENV; >> - save package, write metadata, lock and other; >> - run npm build and install scripts if need with NODE_ENV=production(if >> MIX_ENV == prod) or NODE_ENV = develompert if (MIX_ENV == dev or MIX_ENV == >> test); >> - make symlinks to executable files if need; >> >> I think problem only in semvers, they use caret ^ for versions, oftem >> this behaviour brakes build. >> Bower, npm don't have override or lock mechanism for fix this behaviour. >> Yarn try solve this problems, but many packages can't build(some issues >> open more than year), now they have 783 open issues. >> >> I think need simple functionality: >> npm.docs - open npmjs.com/package/[PACKAGE] >> <http://npmjs.com/package/%5BPACKAGE%5D> >> npm.info - print info >> npm.outdated - print outdated packages >> npm.search - search package >> >> May be good have many repos, and tools for manage npm repos. >> And I think don't need functionality for publishes packages in npm repo >> with mix. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "elixir-lang-core" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/elixir-lang-core/f6fac075-949a-45d5-9781-4f8077fb364b% >> 40googlegroups.com >> <https://groups.google.com/d/msgid/elixir-lang-core/f6fac075-949a-45d5-9781-4f8077fb364b%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "elixir-lang-core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/elixir-lang-core/CAFsaqD_722qJj-YUoyo26sPLTSWaxX72X9sPJkoWzMZA > u0%2BoWg%40mail.gmail.com > <https://groups.google.com/d/msgid/elixir-lang-core/CAFsaqD_722qJj-YUoyo26sPLTSWaxX72X9sPJkoWzMZAu0%2BoWg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "elixir-lang-core" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elixir-lang-core/CAGnRm4%2ByxQVzEkNs0LNVbjKweFFj0-NOhdM6WQf4mc8_MNOJeg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
