Your message dated Mon, 10 May 2021 13:45:03 +0200
with message-id <[email protected]>
and subject line Re: [Pkg-javascript-devel] Bug#988307: eslint --init fails 
with "cannot find module 'inquirer'
has caused the Debian Bug report #988307,
regarding eslint --init fails with "cannot find module 'inquirer'
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
988307: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=988307
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: eslint
Version: 5.16.0~dfsg+~4.16.8-5
Severity: important

Dear Maintainer,

Immediately after an installation of eslint, running eslint --init
yields:

        Error: Cannot find module 'inquirer'
        Require stack:
        - /usr/share/nodejs/eslint/lib/config/config-initializer.js
        - /usr/share/nodejs/eslint/bin/eslint.js
        at Function.Module._resolveFilename 
(internal/modules/cjs/loader.js:815:15)
        at Function.Module._load (internal/modules/cjs/loader.js:667:27)
        at Module.require (internal/modules/cjs/loader.js:887:19)
        at require (internal/modules/cjs/helpers.js:74:18)
        at Object.<anonymous> 
(/usr/share/nodejs/eslint/lib/config/config-initializer.js:14:16)
        at Module._compile (internal/modules/cjs/loader.js:999:30)
        at Object.Module._extensions..js 
(internal/modules/cjs/loader.js:1027:10)
        at Module.load (internal/modules/cjs/loader.js:863:32)
        at Function.Module._load (internal/modules/cjs/loader.js:708:14)
        at Module.require (internal/modules/cjs/loader.js:887:19)

I see there's a node-inquirer in recommends; that currently has no
installation candidate on my system, but this behaviour would suggest
this should really be a depends -- or, perhaps that a line or two on how
to run eslint without it in the manpage or a README.Debian would be
helpful.

Incidentally, trying with eslint --no-eslintrc I also get a missing 
dependency:

        There was a problem loading formatter: ./formatters/stylish
        Error: Cannot find module 'text-table'
        Require stack:
        - /usr/share/nodejs/eslint/lib/formatters/stylish.js
        - /usr/share/nodejs/eslint/lib/cli-engine.js
        - /usr/share/nodejs/eslint/lib/cli.js
        - /usr/share/nodejs/eslint/bin/eslint.js

-- perhaps node-table needs to be promoted to depends, too?

Thanks,

           Markus


-- System Information:
Debian Release: bullseye/sid
  APT prefers testing-security
  APT policy: (500, 'testing-security'), (500, 'testing')
Architecture: i386 (x86_64)

Kernel: Linux 5.11.11 (SMP w/4 CPU threads)
Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /bin/bash
Init: sysvinit (via /sbin/init)

Versions of packages eslint depends on:
ii  node-ajv                                6.12.6-2
ii  node-concat-stream                      2.0.0-1
ii  node-debug                              4.3.1+~cs4.1.5-1
ii  node-doctrine                           3.0.0-2
ii  node-eslint-scope                       5.1.1-1
ii  node-eslint-utils                       2.1.0-3
ii  node-eslint-visitor-keys [node-types-e  2.0.0+~0.0.45-1
ii  node-espree                             7.3.1~dfsg1-1
ii  node-esquery                            1.3.1~ds-3
ii  node-estraverse                         5.2.0-1
ii  node-esutils                            2.0.3-1
ii  node-file-entry-cache                   6.0.0+~3.0.4+~2.0.0+~1.0.0+~2.0.1-1
ii  node-functional-red-black-tree          1.0.1+20181105-4
ii  node-glob                               7.1.6+~7.1.3-1
ii  node-globals                            13.5.0-1
ii  node-ignore                             5.1.4-5
ii  node-imurmurhash                        0.1.4-1.1
ii  node-json-schema [node-types-json-sche  0.3.0+~7.0.6-1
ii  node-json-stable-stringify              1.0.1+~cs5.1.32-1
ii  node-levn                               0.3.0+dfsg-4
ii  node-lodash                             4.17.21+dfsg+~cs8.31.173-1
ii  node-mkdirp                             1.0.4+~1.0.1-1
ii  node-optionator                         0.9.1+dfsg-1
ii  node-path-is-inside                     1.0.2-1.1
ii  node-progress                           2.0.3-1
ii  node-regenerate-unicode-properties      8.2.0+ds-1
ii  node-regexpp                            3.1.0-4
ii  node-resolve-from [node-import-fresh]   5.0.0+~3.1.0+~3.3.0+~2.0.0-1
ii  node-semver                             7.3.4-1
ii  node-strip-json-comments                3.1.1-1
ii  nodejs                                  12.21.0~dfsg-4

Versions of packages eslint recommends:
ii  node-chalk       4.1.0-1
pn  node-inquirer    <none>
ii  node-js-yaml     3.14.1+dfsg+~3.12.6-2
ii  node-strip-ansi  6.0.0-2
pn  node-text-table  <none>

Versions of packages eslint suggests:
pn  node-babel-code-frame  <none>
pn  node-babel-eslint      <none>
ii  node-esprima           4.0.1+ds+~4.0.2-2
pn  node-esprima-fb        <none>
pn  node-table             <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Hi Markus,

Quoting Markus Demleitner (2021-05-10 10:39:47)
> Immediately after an installation of eslint, running eslint --init
> yields:
> 
>         Error: Cannot find module 'inquirer'
[...]
> I see there's a node-inquirer in recommends; that currently has no 
> installation candidate on my system, but this behaviour would suggest 
> this should really be a depends

"Recommends" means needed "in all but unusual installations":
https://www.debian.org/doc/debian-policy/ch-relationships.html#binary-dependencies-depends-recommends-suggests-enhances-pre-depends

You mention that you cannot install node-inquirer - I don't know why 
that is, but suspect it to be an issue with your system setup rather 
than with the package.


> -- or, perhaps that a line or two on how to run eslint without it in 
> the manpage or a README.Debian would be helpful.

I agree that output could be nicer.  I doubt that will happen, though: 
Upstream most likely is not interested (they don't distinguish between 
dependencies and recommendations like in Debian), and I don't expect to 
take time to patch the code for such detailed polish.

If you think differently, then I encourage you to file a bug upstream 
about improving the error message-

You may also propose a patch to improve the error message, that could be 
applied to the Debian package even if upstream does not want it.  
Beware, though, that I will likely accept only a small patch, because 
otherwise it could cause a maintenance burden.


Thanks for reporting this - I really appreciate bugreports, even though 
in this case I disagree that there's a bug here.


Kind regards,

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: signature


--- End Message ---
-- 
Pkg-javascript-devel mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-javascript-devel

Reply via email to