Dave has got a good point. We might as well release it IF we fix it up. I tried to use paramedic for my personal plugin projects as well but in it's current state it was hard to get running properly.
With all the other projects we have in mind for Cordova I wouldn't give paramedic a high priority personally but if someone has the time to clean it up, improve and document it, it could be valuable for our testing and every plugin developer. I'm +1 on removing things like Sauce Labs and Appium if they are not used or have license issues. On December 3, 2025, Dave Alden <[email protected]> wrote: > As a plugin author, I've found this tool to be very useful in > validating > end-to-end plugin functionality across the web/native bridge. > For example I baked in automated tests using paramedic in a new plugin > I > released a few weeks ago: https://github.com/dpa99c/cordova-plugin- > wearable > > I would advocate releasing it publicly and actively encouraging 3rd > party > plugin developers to make use of it in the plugin development > lifecycle. > Admittedly it currently lacks clear developer documentation - I have > mostly > used existing internal plugins for example usage. > But IMO, encouraging use of this tool as part of the plugin > development > workflow would lead to less buggy plugins which are backed and > validated by > automated tests. > And with the advent of AI tools to assist, writing tests in no longer > the > slow, laborious process it used to be. > > On Wed, Dec 3, 2025 at 6:53 AM Bryan Ellis <[email protected]> wrote: > > > This tool hasn't been maintained frequently, but it has played a > role in > > testing our plugins. > > > > I would even say this tool is more of an internal testing utility > rather > > than something we release or announce publicly. > > > > It appears the tool was last published to the npm registry [1] over > 10 > > years ago, but I believe this was before it was contributed to our > project. > > Based on the package metadata in the npm registry, the listed source > > repository points to a personal GitHub account rather than our > official > > Apache repository. > > This likely suggests that we have never officially released this > tool > > publicly since it was contributed to Apache Cordova. > > > > With that in mind, do we actually want to make an official release, > or > > should we keep this as an internal tool? > > > > There was a ticket in 2019 requesting for a new release, but nothing > ever > > happened. > > > > If we want to keep it as an internal tool, we should probably > deprecate the > > npm package so it's clear that this is internal-only and will not be > > updated. > > > > If we decide to update the npm package instead, in my opinion, we > would > > need to skip the `1.0.0` release and prepare a `2.0.0`, because: > > > > * The current `main` branch is not in a releasable state. It might > work, > > but is blocked by other factors. > > * Changes required to prepare a release contains major breaking > changes > > that would remove things that might have been used in the past. > > > > What would be removed: > > > > **SauceLabs** [2] – Cordova has not used this third-party service in > a long > > time and has never been kept up to date. Some features are behind a > paid > > plan, so we can't properly evaluate or support it, and historically > we saw > > issues. > > > > **Appium** [3] – While useful, the version we currently include > should no > > longer be used. We also can't upgrade to the latest major versions > because > > they introduce a transitive dependency with a license we cannot > support. > > > > **Windows Platform** [4] - Since the Cordova-Windows platform has > been > > deprecated for a long time, we need to remove this as part of the > cleanup. > > > > Other breaking changes, cleanup, would also be introduced in > `2.0.0`: > > > > * Bump dependencies & node engine requirement [5] > > * Remove Android 7-11 from test plan. > > > > Does anyone have any thoughts on what we should do with Cordova- > Paramedic > > regarding its release to npmjs? > > * Should we prepare a new release? > > * Should we deprecate the package but keep it as an internal tool? > > > > References: > > [1] https://www.npmjs.com/package/cordova-paramedic > > [2] https://github.com/apache/cordova-paramedic/pull/273 > > [3] https://github.com/apache/cordova-paramedic/pull/274 > > [4] https://github.com/apache/cordova-paramedic/pull/277 > > [5] https://github.com/apache/cordova-paramedic/pull/275 > > [6] https://github.com/apache/cordova-paramedic/pull/278 > >
