You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error while parsing /Users/corneliusromer/code/loculus/website/node_modules/react-toastify/dist/react-toastify.esm.mjs
Line 4, column 0: Unknown token at 15459, expected: "}", actual: ""
`parseForESLint` from parser `/Users/corneliusromer/code/loculus/website/node_modules/astro-eslint-parser/lib/index.js` is invalid and will just be ignored
Error while parsing /Users/corneliusromer/code/loculus/website/node_modules/react-toastify/dist/react-toastify.esm.mjs
Line 4, column 0: Unknown token at 15459, expected: "}", actual: ""
`parseForESLint` from parser `/Users/corneliusromer/code/loculus/website/node_modules/astro-eslint-parser/lib/index.js` is invalid and will just be ignored
/Users/corneliusromer/code/loculus/website/src/layouts/BaseLayout.astro
3:32 warning Parse errors in imported module 'react-toastify': parser.parse is not a function (undefined:undefined) import/no-deprecated
I do'nt quite know why this error surfaced only now. It happens when I upgrade eslint-plugin-import from 2.29.1 to 2.31.0 - many components seem to come together here creating a strange end result.
Before You File a Bug Report Please Confirm You Have Done The Following...
What version of ESLint are you using?
8.57.0
What version of
eslint-plugin-astro
are you using?1.3.1
What did you do?
cd website && npm ci
.npm run check-format
.What did you expect to happen?
No errors
What actually happened?
Link to Minimal Reproducible Example
loculus-project/loculus@654535a
Additional comments
I do'nt quite know why this error surfaced only now. It happens when I upgrade
eslint-plugin-import
from 2.29.1 to 2.31.0 - many components seem to come together here creating a strange end result.Here's the dependabot PR that first surfaced this: loculus-project/loculus#3231
Let me know if I should file an issue elsewhere, for now there is at least some strange parsing going on here?
The text was updated successfully, but these errors were encountered: