Replies: 3 comments 5 replies
-
I think there are lots of benefits to the extension CLI and we should keep it, which it sounds like you agree with. Beyond that I don't care. If there's a way to make it nicely interoperable with standard NPM tooling (via some discovery process we add to Appium as a fallback or additional search parameter for appium home), then that's cool too. I guess I would just be interested to consider a proposal sketch that you have in mind as the next step. |
Beta Was this translation helpful? Give feedback.
-
IIRC this can be accomplished with
I'll test with You mentioned some time ago that you had clients that didn't want to deal with |
Beta Was this translation helpful? Give feedback.
-
I can confirm that we can create an |
Beta Was this translation helpful? Give feedback.
-
I understand the reasons for providing a CLI to manage extensions (
appium driver
/appium plugin
), but I am wondering if anyone would want to just usenpm
(or Yarn or pnpm or w/e) to install extensions?Setting the implementation discussion or technical challenges aside for a moment, there are drawbacks to the current strategy:
package.json
or env, and only as apostinstall
hook).postinstall
hooks will forever remain supported or enabled by default. This would mean extensions would need manual installation.npm audit
, dependabot, license compliance checks like FOSSA, etc.To be clear, I'm not proposing that we abandon e.g.,
appium driver install
, because it's undoubtedly quite useful for many end-users. However, this isn't everyone, and I believe we could find an alternative means of extension management--one which would offer the usual benefits of ecosystem conventions to which Node.js/JS developers are accustomed.Looking for feedback from @jlipps especially 😄
Beta Was this translation helpful? Give feedback.
All reactions