Fix the action logger running in production

The condition guarding the redux-logger middleware tested for the
opposite of what it meant to test, so the logger was installed in
production builds and left out during development. It relied on a
build-time constant that Vite substitutes, so the check folded away
and the middleware ended up unconditional in the shipped bundle.

The check now uses Vite's own environment flags. Test runs are
excluded as well, because Vite reports development mode there too and
the logger would otherwise write into the output of every test that
dispatches an action. This also drops the file's last reference to the
Node process global, and with it an eslint exception.

The redux-logger dependency still reaches the bundle even though
nothing calls it now, because it is CommonJS and tree shaking cannot
remove it. Dropping the dependency is separate work.

Author: longsleep

identifier/src/store.js

@@ -8,8 +8,11 @@ const middlewares = [
   thunkMiddleware
 ];
 
-if (process.env.NODE_ENV !== 'development') { // eslint-disable-line no-undef
-  middlewares.push(createLogger()); // must be last middleware in the chain.
+// The action logger is for interactive development only and must not be part of
+// a production build. Test mode is excluded as well, matching how
+// vite.config.js gates the checker plugin.
+if (import.meta.env.DEV && import.meta.env.MODE !== 'test') {
+  middlewares.push(createLogger()); // Must be last middleware in the chain.
 }
 
 const composeEnhancers = window.__REDUX_DEVTOOLS_EXTENSION_COMPOSE__ || compose;