Hi!
For example, like ios project can pass "packagename":
path=>"../../node_modules/packagename/ios/" to include the package, it's
not using npm link, but a logic should be into the "weex plugin add"
command.
For now, if you want to publish your ios package, you have to publish your
ios plugin in
Hi!
How does that local path link work? You mean npm link?
Sure, after I figure this out In think I can help implementing the GitHub/local
path plugin.
I have another (probably noob) question: I also have to publish my plugin in
cocoa pods, if it will be used on iOS, right?
Tiago
On 15 Mar 2
Hi, Tiago
I'm a developer of weexpack.
It's a very useful suggestion, I very much agree with this scenes you said,
the plugin should support local and other remote paths which are also
planned to be implemented, we have implemented similar logic in `weex
create` command. What is needed is to modi
Hi!
I am developing a plugin that is not quite ready for the public, but still I
would like to use internally in my project. Is there a way to install the
plugin without publishing it on npm? After some tests and reading the relevant
code*, it seems like it is not possible.
Other plugin system
