Skip to content

BUG: Scan (sometimes?) fails with dual-licensed packages - argument.trim is not a function #111

Description

@snspinn

Trying to do a scan on a fairly old repo. Can't publish the list of packages but I'm only mentioning its age because newer repos get scanned fine. When scanning, I get the error argument.trim is not a function.

Description

Running npx --verbose @onebeyond/license-checker scan --failOn GPL-1.0-or-later.

Also tested with different node/npm version combinations, same behaviour.

Expected Behavior

Should scan the repo and output a licence report file.

Actual Behavior

Full terminal output:

npm verb cli [
npm verb cli   '/home/username/.proto/tools/node/16.20.2/bin/node',
npm verb cli   '/home/username/.proto/tools/npm/7.24.2/bin/npm-cli.js',
npm verb cli   'exec',
npm verb cli   '--loglevel',
npm verb cli   'verbose',
npm verb cli   '--',
npm verb cli   '@onebeyond/license-checker',
npm verb cli   'scan',
npm verb cli   '--failOn',
npm verb cli   'GPL-1.0-or-later'
npm verb cli ]
npm info using npm@7.24.2
npm info using node@v16.20.2
npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:/home/username/.proto/tools/npm/7.24.2/npmrc Completed in 1ms
npm timing config:load:builtin Completed in 1ms
npm timing config:load:cli Completed in 2ms
npm timing config:load:env Completed in 0ms
npm timing config:load:file:/home/username/Projects/apps/project/.npmrc Completed in 0ms
npm timing config:load:project Completed in 1ms
npm timing config:load:file:/home/username/.npmrc Completed in 1ms
npm timing config:load:user Completed in 1ms
npm timing config:load:file:/home/username/.proto/tools/node/16.20.2/etc/npmrc Completed in 1ms
npm timing config:load:global Completed in 1ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 1ms
npm timing config:load:setEnvs Completed in 0ms
npm timing config:load Completed in 8ms
npm timing npm:load:configload Completed in 8ms
npm timing npm:load:setTitle Completed in 0ms
npm timing npm:load:setupLog Completed in 1ms
npm timing config:load:flatten Completed in 2ms
npm timing npm:load:cleanupLog Completed in 1ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load:projectScope Completed in 1ms
npm timing npm:load Completed in 21ms
npm http fetch GET 200 https://registry.npmjs.org/@onebeyond%2flicense-checker 328ms (cache revalidated)
npm timing arborist:ctor Completed in 1ms
npm timing arborist:ctor Completed in 0ms
npm timing arborist:ctor Completed in 0ms
npm timing arborist:ctor Completed in 0ms
argument.trim is not a function
npm timing command:exec Completed in 5061ms
npm verb exit 1
npm timing npm Completed in 5236ms
npm verb code 1

Possible Fix

N/A

Steps to Reproduce

Cannot provide steps to reproduce right now but will work on doing so.

Context

Preventing use of the scan tool entirely.

Your Environment

  • Version used:
  • Environment name and version (e.g. Chrome 39, node.js 5.4): node 16.20.2; npm 7.24.2
  • Operating System and version (desktop or mobile): Ubuntu 22.04
  • Link to your project: N/A

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions