"Cannot find module" when linting project in sub folder using browserslist about vscode-stylelint HOT 10 CLOSED

Unfortunately yes.

I found this shared browserlist config https://www.npmjs.com/package/@cleverfranke/browserslist-config
Perhaps you can test with

.browserslistrc

# You can see what browsers were selected by your queries by running:
#   npx browserslist

extends @cleverfranke/browserslist-config

from vscode-stylelint.

Closing as upstream bug.

from vscode-stylelint.

What can I do to move this along?

from vscode-stylelint.

Can you confirm this is still happening with the latest version of the extension? I ran a similar test where I moved a project into a subfolder on the latest version of the extension and it seemed to work, however, I wasn't using browserslist.

from vscode-stylelint.

Looks like the problem is at this line in browserslist:

var queries = require(require.resolve(name, { paths: ['.'] }))

Since the paths passed to require.resolve only reference the current working directory, since the extension is not running in the context of the subfolder but in the workspace, it can't resolve the package. You can replicate this issue in the terminal by running Stylelint from the workspace folder.

@ai I tested changing this line to

var queries = require(require.resolve(name, { paths: ['.', ctx.path] }))

and it seems to fix the problem. Am I correct to assume that this may be the right fix for this issue?

from vscode-stylelint.

@adalinesimonian please send PR to Browserslist.

from vscode-stylelint.

Done: browserslist/browserslist#638

from vscode-stylelint.

@adalinesimonian I'm trying to figure out how to get the newly released [email protected] updated in this extension. It appears as if it's coming from these packages:

• @babel/helper-compilation-targets
• caniuse-lite
• core-js-compat

So to get it working they need to update their browserslist version and then this extension needs to use their new versions.
Is that the correct course of action? Or am I missing something :)?

from vscode-stylelint.

This extension doesn't bundle browserslist (or Stylelint); it's sourced from your project's dependencies. You'll need to update the version of browserslist in your project, after which I think you'll be good.

from vscode-stylelint.

I see, thank you

from vscode-stylelint.