solito: Some problems with Eslint and Typescript

Hey @nandorojo, huge fan of your work here

I’ve created a repo using create-solito-app yesterday, but I’m having some issues. Maybe I’m missing something, but I don’t have much knowledge on monorepos

Eslint

With Eslint, next/ has its own .eslintrc.js. How can I extend with my own config there? I do have my own Eslint npm package. One side note, running the nextjs app was not working until I added this:

module.exports = {
  extends: 'next',
  root: true,
  rules: {
    '@next/next/no-html-link-for-pages': ['error', 'apps/next/pages/'],
  },
};

Maybe this should be in the template?

Typescript

And with Typescript, my intellisense is a mess on Vscode. Some auto imports simply just not work.

Example: I just deleted MotiLink import from this template file, but Typescript can’t find MotiLink to import Screen Shot 2022-04-08 at 10 48 35

This was only one example, but I’m having this same problem with some other packages, depending from where I try to import them.

Currently, I’ve just added some devDependencies on root, like husky, lint-staged and commitlint for example.

Can you help me out?

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 18 (11 by maintainers)

Most upvoted comments

Hey I think I solved the ESLint issue in this commit btw! https://github.com/nandorojo/solito/commit/610be58de58a81911a8ce8a7c227c070be16c258

I updated the root lint file and deleted the linter file in apps/next (though you don’t have to do that).

can you try upgrading solito to 0.0.25 and see if that fixes it?

yes, and i think i found the solution

hey! you mentioned a number of different questions here. i’ll try to answer later today