fix: switch to memory webpack cache

Author: Filipoliko

.changeset/quiet-teal-mice.md

@@ -0,0 +1,5 @@
+---
+"@ima/cli": patch
+---
+
+Switch from `filesystem` to `memory` webpack cache configuration. The filesystem cache was causing issues with webpack v5.100.0+, which led to `ima dev` command failing if a cache from a previous run existed and files in node_modules were changed. We might consider switching back to `filesystem` cache once we figure out the root cause of the issue.

packages/cli/src/webpack/config.ts

@@ -26,8 +26,6 @@ import { GenerateRunnerPlugin } from './plugins/GenerateRunnerPlugin';
 import { ManifestPlugin } from './plugins/ManifestPlugin';
 import { createProgress } from './plugins/ProgressPlugin';
 import {
-  createCacheKey,
-  IMA_CONF_FILENAME,
   createPolyfillEntry,
   createDevServerConfig,
   getCurrentCoreJsVersion,
@@ -283,24 +281,7 @@ export default async (
       hotUpdateMainFilename: `${outputFolders.hot}/[runtime].[fullhash].hot-update.json`,
       ...(isServer && { library: { type: 'commonjs2' } }),
     },
-    cache: {
-      type: 'filesystem',
-      name: `${name}-${ctx.command}-${mode}`,
-      version: createCacheKey(ctx, imaConfig, {
-        ...devServerConfig,
-        $Debug: isDebug,
-        coreJsVersion: 'core-js',
-        devtool,
-      }),
-      store: 'pack',
-      hashAlgorithm: 'xxhash64',
-      memoryCacheUnaffected: true,
-      buildDependencies: {
-        imaCli: [require.resolve('@ima/cli')],
-        imaConfig: [path.join(rootDir, IMA_CONF_FILENAME)],
-        defaultConfig: [__filename],
-      },
-    },
+    cache: { type: 'memory' },
     optimization: {
       minimize: ctx.command === 'build' && !isServer,
       minimizer: [