bug: internal vscode module output

Fixes #698

Author: gnikit

CHANGELOG.md

@@ -70,6 +70,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/).
 
 ### Fixed
 
+- Fixed bug where the linter's internal cache directory would not always exist
+  ([#698](https://github.com/fortran-lang/vscode-fortran-support/issues/698))
 - Fixed bugs in relative path resolution for `fortls`
   ([#693](https://github.com/fortran-lang/vscode-fortran-support/issues/693))
 - Fixed issues with linter unittests running asynchronously

src/extension.ts

@@ -47,7 +47,8 @@ export async function activate(context: vscode.ExtensionContext) {
     })
   );
   // Linter is always activated but will only lint if compiler !== Disabled
-  const linterCache = path.join(context.storageUri.fsPath);
+  const linterCache = path.join(context.storageUri.fsPath, 'include');
+  await vscode.workspace.fs.createDirectory(vscode.Uri.file(linterCache));
   const linter = new FortranLintingProvider(logger, linterCache);
   context.subscriptions.push(...(await linter.activate()));
   vscode.languages.registerCodeActionsProvider(FortranDocumentSelector(), linter);

updates/RELEASE_NOTES-unreleased.md

@@ -207,3 +207,6 @@ which is slower but does not suffer from this issue.
 The cache used by the linter should help mitigate any performance issues.
 
 ## 🐛 Bug Fixes 🐛
+
+- Fixed bug where the linter's internal cache directory would not always exist
+  ([#698](https://github.com/fortran-lang/vscode-fortran-support/issues/698))