This pull request allows ignoring version constraint from packages.json

After using the NPM autodiscovery plugin for a while, I realize that It would be better to ignore version constraint by default and to suggest the latest version available regardless of the constraint defined in the package.json

More context from here to understand the initial design.

This new behavior can be enabled/disabled using the new parameter ignoreversionconstraints.
By default it's set to false (no breaking change)

Here is an example

name: testing npm pr
autodiscovery:
  crawlers:
    npm:
      ignoreversionconstraints: true
      only:
        - packages:
            "js-yaml": ""
      #    hasversionconstraint: true
      versionfilter:
        kind: semver
        pattern: majoronly

While working on this, I am also adding a new matchingrule named "hasversionconstraint" to be able to only/ignore npm modules with or without a version constraint.

If a version constraint is detected and the ignoreVersionConstraint flag is set to true, the code initially sets the version filter pattern to a wildcard (*), meaning any version is acceptable. However, if a custom version filter is also defined and the dependency version is not "latest", it attempts to convert the version constraint into a specific version.

If a version constraint exists but ignoreVersionConstraint is false and a version filter is defined, the code logs a warning. This is because the system does not currently support applying both the package's version constraint and an additional version filter at the same time, as there is no clear use case for this scenario.

Finally, if no version constraint is present, the code constructs a default filter pattern that matches versions greater than or equal to the specified dependency version. If a custom version filter is defined, it uses the filter's kind and attempts to generate a more specific pattern.

Test

To test this pull request, you can run the following commands:

cd pkg/plugins/autodiscovery/npm/
go test

Additional Information

Checklist

• I have updated the documentation via pull request in website repository.

Tradeoff

Potential improvement