Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Eslint: Unable to resolve path to module 'vite-plugin-ssr/plugin' as of 0.3.57

See original GitHub issue

As of version 0.3.57:

in vite.config.ts:

import { ssr } from "vite-plugin-ssr/plugin"

results in:

Unable to resolve path to module 'vite-plugin-ssr/plugin'

and anywhere I call getPage:

import { getPage } from "vite-plugin-ssr/client"

results in:

Unable to resolve path to module 'vite-plugin-ssr/client'

This doesn’t happen in 0.3.56, but probably related to adding ESM support?

Issue Analytics

State:
Created 2 years ago
Comments:5 (4 by maintainers)

Top GitHub Comments

1reaction

brilloutcommented, Feb 22, 2022

I see. I’ll write the fix today/tomorrow.

0reactions

brilloutcommented, Feb 23, 2022

Fix released in v0.3.59. It should now work but I didn’t test it; let me know if you still have problems with eslint.

Top Results From Across the Web

Vite.js + Eslint unable to resolve path alias #14667 - GitHub

I managed to set up my vite.config.js so that the app can resolve paths like this: ... Unable to resolve path to module...

Using eslint with typescript - Unable to resolve path to module

You can set the ESLint module import resolution by adding this snippet to your .eslintrc.json configuration file:

eslint/eslint - Gitter

I'm trying to setup eslint-plugin-import but I can't make it work xD ... 6:8 error Unable to resolve path to module '~/components' import/no-unresolved....

ESLint Unable to resolve path to module

Visual Studio 2022 shows errors for tsconfig paths when it's actually able to find them. ... Please fix these issues! ... Thanks for...

Known Problems - Contentlayer

ESLint error: Unable to resolve path to module 'next-contentlayer' (GitHub Issue ); useLivereload hook is needed in some cases (GitHub Issue ) ...