Skip to content

Community Packages with Native ModulesΒ #285

@confused-Techie

Description

@confused-Techie

This list will continue to be updated, as the process is only semi-automated at this time.
This issue will contain a checklist of community packages that contain Native Modules. As many native modules will stop working once we officially role out PulsarNext.

So this list will be a list of the most at risk community packages that will require testing in PulsarNext to verify if they are broken or continue to work.

If a package still works on PulsarNext we can check it off the list to indicate it's still functional, and for everything still on the list we will then want to look even closer to see what can be done to get that package working, or if we will need to anticipate it breaking after the PulsarNext release.

(If more information is needed for this list I have it in the logs of the scripts I'm using to check packages, and it can easily be added along with package names, so feel free to request it's addition)


(For clarity, the names here are the packages name on the Pulsar Package Registry, it links to the packages GitHub, and they are listed in order of downloads. The text after each package is a comma separated list of dependencies that caused them to be flagged)

Note: A warning, if a package fails to install, we won't be able to determine it's native modules and it won't appear on this list, so there is a chance of those packages becoming false negatives for inclusion. Additionally, a package's devDependencies may cause it showing up here to be a false positive.

Packages Checked: 10,777/10,777

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions