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.
