Does not give eslint errors in Webstorm IDE or VSCode about solito

[nandorojo]

See this commit to see the fix: d9e40a4

You can also run npx create-solito-app@latest if you want, but since you already have an app started, you'll probably want to copy over those changes.

Thanks for opening the issue, hope that fixes it on your end! Please let me know if it does.

[RobinLindhout]

When we add

yarn add @next/eslint-plugin-next --dev -W

we got

[RobinLindhout]

When we use

module.exports = {
  extends: 'next/core-web-vitals',
}

as base + yarn add next eslint eslint-config-next --dev -W in the root package it starts working.

But no errors in IDE on not existing properties

[nandorojo]

I was getting issues with ESLint too…I wonder if that eslint file should be in the Next app folder? As you’ll see in the starter, I some ESLint config issues from the new Next.js linter.

[nandorojo]

the image you sent shouldn’t break, since background color accepts any string. Is that what you’re referring to?

When we use

module.exports = {
  extends: 'next/core-web-vitals',
}

as base + yarn add next eslint eslint-config-next --dev -W in the root package it starts working.

But no errors in IDE on not existing properties

[RichardLindhout]

But in your demo video it gave errors when e.g. wrong spacing was being used?

[RichardLindhout]

It does give errors in the terminal though just not in the IDE.

[nandorojo]

It does give errors in the terminal though just not in the IDE.

I had this same issue. I got around it by silently breaking the next lint command with an incorrect ESLint config. Looking into this now for a fix

[RichardLindhout]

I don't know if eslint can understand it if we use eslintrc for expo and in nextjs folder we can use nextjs linting too

[RichardLindhout]

Should be nice if we could use nextjs things only in next project and react native + web linting in packages/app

[nandorojo]

Yeah, that's more of a monorepo question in general. It feels like it should be possible if we extend the ones we want in each folder. That said, I'm a bit confused why this error comes up, only when I install next's ESLint plugin and run yarn build:

yarn run v1.22.5
$ next build
info  - Checking validity of types  

Failed to compile.

./pages/_app.tsx
1:1  Error: Parsing error: The keyword 'import' is reserved

./pages/_document.tsx
1:1  Error: Parsing error: The keyword 'export' is reserved

./pages/index.tsx
1:1  Error: Parsing error: The keyword 'import' is reserved

./pages/user/[id].tsx
1:1  Error: Parsing error: The keyword 'import' is reserved

info  - Need to disable some ESLint rules? Learn more here: https://nextjs.org/docs/basic-features/eslint#disabling-rules
error Command failed with exit code 1.

[nandorojo]

Made some progress with this in the apps/next/.eslintrc.js file:

module.exports = {
  extends: 'next',
}

I also installed @next/eslint-plugin-next in apps/next. Still some errors but it builds.

[nandorojo]

Okay, I think I fixed it!

Put this in .eslintrc.js in apps/next:

module.exports = {
  extends: 'next',
  root: true, // don't check from parent folder
}

And install eslint-config-next inside of apps/next

It looks like root: true fixed it for the monorepo. I think this field should allow what @RichardLindhout proposed:

Should be nice if we could use nextjs things only in next project and react native + web linting in packages/app

[RichardLindhout]

Amazing we will try it out soon!

[RichardLindhout]

Moti is amazing btw <3. First time I used it and it's so easy to write cool animations.