Hi! I have a strange problem with ignoring some files from linting: I have UI error messages from files that must be ignore according my .pug-lintrc config but meantime cli successfully ignore excluded files and doesn't show any errors.

For example my .pug-lintrc file looks like:
{ _My rules here_ "excludeFiles": ["src/pages/**"] }

VScode shows me errors in src/pages/** files.

But cli command npx pug-lint src/pages doesn't inform me about any errors in src/pages/** files.
I can't understand why is it happening. I will be happy for any help with it issue.

OS: Ubuntu 21.04 hirsute
DE: KDE 5.80.0 / Plasma 5.21.4
Vscode 1.57.0
pug-lint: 2.6.0
vscode-pug-lint: 2.3.0

• If workspace don't contain config file
• If package.json don't contain config section for puglint

I installed pug-lint by yarn global add pug-lint and can run it with bash and fish terminals, but vscode-puglint works only after npm i -g pug-lint.

In my project I have server and client code in separate sub-directories of my project directory. If I put the .pug-lintrc file in the project root, the plugin sees it and works properly. If I put the .pug-lintrc file in the client directory (since it's client-specific) the plugin does not see the file, even if the .pug file is in a child directory of where the rule set is. It should climb up the directory tree from the file until it finds a rule set.

First: This plugin has done a great job during the last years -- thanks for this!

We have recently restructured our repository and split it into sub-projects and during this, we have moved some configuration files to subdirectories. The structure now looks like this:

+-- subproject-a
|     +-- src
|     |     +-- pug-files
|     +-- .pug-lintrc.js
|     +-- package.json
+-- subproject-b
+-- subproject-c

Since then, the puglint plugin unfortunately no longer works for us. If I interpret the code correctly, the plugin only seems to check the root path only. (this is different to how e.g. VS Code behaves -- there I can e.g. have individual and different tsconfig.json instances for the sub projects)

The following workarounds seem to work:

• additionally install pug-lint in the repository’s root, and add a .pug-lintrc.js there as well (our build process requires it to be present in subproject-a). To reduce duplication, I used:

  module.exports = require('./subproject-a/.pug-lintrc.js');
  

• open subproject-a instead of the repo’s root -- this way, unfortunately we’re losing context.

Is there something I’m missing or a better fix or workaround for this?

Hi

With pugjs/pug-lint#79, I'm going to be dropping support for presets in favour of extending config from external resources, so just wanted to let you know as I see you are using one in some of your tests

I would like it if the extension ran pug-lint from node_modules instead of globally, because this has been my experience.

1. Install the extension.
2. There are no error messages and nothing happens.
3. Install pug-lint globally.
4. Now it works.

This means that I have to make sure everyone on my team runs the same pug-lint version, and I have to update a wiki telling everyone which version of pug-lint to install on their machine. When people forget to do this, they check in code with problems, and don't know about them until the CI server tells them. It's easier if the extension just detects pug-lint from node_modules, and runs that.

A lot of linter extensions in vscode expose a configFile setting, which allows setting the path to the rule set file. Would be great this one had it too!

Is it possible to get support for files such as .vue which contain a <template> <style> and <script> tag?

Example:

<template lang='pug'>
  #app
    | this is my app
</template>

<script>
</script>

<style lang='scss'>
</style>

When adding the plugin to VSCode, the first thing I get is the following error message

Cannot find module "pug-lint-config-build/.pug-lintrc" to extend

What does it mean and are there any fixes for this?

Running on Windows 8.1 x64, I just upgraded VSCode to latest 1.31.0, and installed your plugin, enabled it to run on save in settings.

I have pug-lint installed globally by npm i -g pug-lint. Source files are accessed remote via ssh-fs.

On every save I get the error The "path" argument must be of type string. Received type object,
which I guess is because of the pug-lint --config <path> parameter is either missing or wrong.

So, what are my options in this scenario?

Is there somewhere I can set the --config <path> ?