Lots of errors produced in WebStorm IDE with this plugin

[ekilah]

Describe the bug
When including this plugin in my tsconfig.json, the Intellij WebStorm IDE reports hundreds of errors that look like this:
Error:(54, 33) TS1155: 'const' declarations must be initialized.

When I remove this plugin, these errors go away.

To Reproduce
Steps to reproduce the behavior:
Use WebStorm in a project with this plugin. My tsconfig using ts 3.9.5:

{
  "compilerOptions": {
    "outDir": "build/dist",
    "module": "esnext",
    "target": "es5",
    "lib": ["es6", "dom"],
    "sourceMap": true,
    "allowJs": true,
    "jsx": "react",
    "moduleResolution": "node",
    "baseUrl": ".",
    "rootDir": ".",
    "allowSyntheticDefaultImports": true,
    "esModuleInterop": true,
    "paths": {
      "~/*": ["src/*"]
    },
    "importsNotUsedAsValues": "preserve",
    "forceConsistentCasingInFileNames": true,
    "noImplicitReturns": true,
    "noImplicitThis": true,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "suppressImplicitAnyIndexErrors": true,
    "noUnusedLocals": true,
    "isolatedModules": true,
    "plugins": [
      {
        "name": "typescript-plugin-css-modules",
        "options": {
          "customMatcher": "\\.css$"
        }
      }
    ]
  },
  "exclude": [
    "./node_modules",
    "build",
    "scripts",
    "acceptance-tests",
    "webpack",
    "src/setupTests.ts"
  ]
}

The TypeScript window in the IDE will call the TS service and find errors for you.

Expected behavior
These errors wouldn't show up.

Screenshots
see above.

another very simple example:

Desktop (please complete the following information):

• OS: Mac OSX Catalina

Additional context
We use CSS modules and some PostCSS features, though these errors seem to pop up in files that don't do anything fancy like PostCSS's nesting, too.

[mrmckeb]

I was just thinking about wha could cause this and it might be to do with this:

typescript-plugin-css-modules/src/helpers/createExports.ts

Lines 42 to 44 in f9af73d

	declare const classes: {
	${processedClasses.map(classNameToProperty).join('\n ')}
	};

It seems to be only occurring in IntelliJ editors, so it might be to do with the way they use (or don't use) the TypeScript Language Service.

As a quick test, could you edit the source code, so that it declares with let instead?

[ekilah]

@mrmckeb Sorry it took so long to try this out, been busy!

Yes, that change does seem to fix the issue (or at least, get rid of the errors). It's annoying to test because it seems like I have to quit/restart Webstorm for it to decide to consume the changes in my package.json 😛 , but I confirmed the hundreds of errors disappeared with this change.

Added that to a PR: #100

[mrmckeb]

Thanks @ekilah, I've replied to the PR.

[ekilah]

Hm, I tried the beta today and I get the same errors. I realize the reason the errors were gone when using my patch was probably because I was using the following in package.json: "typescript-plugin-css-modules": "https://github.com/ekilah/typescript-plugin-css-modules#patch-2",

That doesn't get 'built', so the directory in node_modules only has TS files. Maybe this was just preventing the editor from running the plugin at all, and it was failing silently.

I changed package.json from prepublishOnly to prepare as suggested by https://stackoverflow.com/questions/40528053/npm-install-and-build-of-forked-github-repo and installed my patch again, and was able to see errors still. So, I guess there is another issue causing this.

[mrmckeb]

You can also install locally by using something like yarn add file:../../path/to/module and it works. Or you can try Yarn/npm link.

I assume you're right, it wasn't running at all.

What is the error you're seeing now @ekilah?

[ekilah]

The same error as the original post, with or without my patch and with or without your beta, unfortunately