Re: plugins, npm, and package.json ...other art

[Steven Gill <st...@gmail.com>]

thanks for sharing Brian.

I posted the nativescript one in the whitelist release vote thread a few
days ago. Not the most visible place.

I really like the nativescript proposal. Specifically the engine tag to
manage versions of supported platforms and how they are proposing to handle
platform configuration (json transformation + separate configuration files
that get merged in).

I also like how they are giving each platform a dependency manager instead
of relying on npm for dependency management. The current npm dependency
system won't work for our plugins. Peer dependencies have been turned into
warnings instead of installing the plugin as a sibling. If we nest
dependencies, we will start seeing problems of two different versions of
one plugin being installed. Causing all sorts of havoc.





On Thu, Apr 2, 2015 at 11:39 PM, Jesse <pu...@gmail.com> wrote:

> Yeah, the more I look at these, the more overlap I see.
> I am surprised how narrowly scoped the react discussion is. iOS only? Is
> Android not even on their radar?
>
> @purplecabbage
> risingj.com
>
> On Thu, Apr 2, 2015 at 5:51 PM, Brian LeRoux <b...@brian.io> wrote:
>
> > both reactnative [1] and nativescript [2] treading into the territory
> >
> > fleeting hope we could share work/code but probably good everyone does a
> > bit of homework on the topic
> >
> > [1] https://github.com/facebook/react-native/issues/235
> > [2] https://github.com/NativeScript/NativeScript/issues/25
> >
>