You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@capawesome-team/capacitor-nfc is a private package not found in npm, so it can't be indexed by the registry. You'll see that when it inspects the plugin it errors:
Inspecting 106 of 1146: @capawesome-team/capacitor-nfc
Error: @capawesome-team/capacitor-nfc was not found on npm.
Hey @dtarnawsky, thanks for your answer!
From my pov, the registry should support both public and private packages. There will always be private packages (e.g. for paying customers). Of course, you can't expect private packages to be indexed automatically, but if they were added manually to the plugins.txt file, then they should also appear as search results with the information available.
The @ionic-enterprise packages are also displayed even though they are private:
I would like to see the same for the community packages.
If the problem is the missing meta information, then #34 would be a solution.
There seems to be some problems with the search. Some plugins are not found.
Example:
nfc
The following plugin is not listed, but is included in
plugins.txt
:@capawesome-team/capacitor-nfc
The text was updated successfully, but these errors were encountered: