Even hex itself is not part of elixir core or mix, why would we have npm?

Michał.

On 8 Jun 2017, 10:21 +0200, Aleksandr Pavliutin 
<[email protected]>, wrote:
> As I undestand, mix part of Elixir *core*. Without mix you can't build 
> application more difficult than "hello world".
>
> I don't agree with Justin, this functionality not for third party libraries, 
> because mix have 90% for work with npm.
> I can undestand this position if I propose make rust projects with mix using 
> cargo or something like this.
>
> Most of all phoenix projects have package.json and default build instrustion 
> "mix deps.get && npm install".
> It would be great if all npm deps and builds store in main tree (deps and 
> _build/[MIX_ENV] folders). All brunch scripts would be more simple,
> because they work with one dir in all projects.
>
> Mix have buildin functionality in core for make c/c++ projects and erlang 
> with rebar. And some erlang developers use mix for build they projects 
> instead rebar.
>
> четверг, 8 июня 2017 г., 1:57:46 UTC+3 пользователь José Valim написал:
> > 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]
> > > > > > 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/msgid/elixir-lang-core/f6fac075-949a-45d5-9781-4f8077fb364b%40googlegroups.com.
> > > > > > 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-YUoyo26sPLTSWaxX72X9sPJkoWzMZAu0%2BoWg%40mail.gmail.com.
> > > >
> > > > 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/21b8086b-a244-4343-9612-d2bab78fdef5%40googlegroups.com.
> 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/6cd0f116-31fd-4b8d-aba8-0240cde34192%40Spark.
For more options, visit https://groups.google.com/d/optout.

Reply via email to