ignite VS ESLint

Jamon Holmgren, CTO at Infinite Red, joins Nick Taylor to discuss the Ignite project, https://github.com/infinitered/ignite, a battle-tested React Native boi...

You'll learn lot more without Expo. It makes things lot easier/faster but will give you problems later. I recommend you to start with cli, and if you want to avoid tedious tasks of setting up things, go ahead with Ignite or another boilerplate that has already all the basic libraries set up (react navigation, state, UI, etc.) so you just can begin with your project logic/code https://github.com/infinitered/ignite

You should check out the react native boilerplate by Ignite: https://github.com/infinitered/ignite

I recently picked up react native, though I had a good amount of experience with React already and much of it is similar. Except for working with the file system and tooling.

One good boilerplate I’d recommend having a look at is https://github.com/infinitered/ignite not a course but possibly a good resource to learn from.

Check out React Native Ignite

I've been using the Ignite boilerplate (with Expo enabled) and I'm quite happy with it. It contains everything I need, nicely structured.

I get it. If you're just here to find a good, working ESLint configuration for a NextJS project, then look no further. Copy what's below. Although, it's probably out of date, so you can find a version that's been updated since I published this post in my open source project Historio ➡️ in Github here ⬅️.

Does the library run in production, or is it limited to development or testing environments? Vulnerabilities in libraries like mocha or eslint can typically wait, while issues in runtime-critical libraries like express need immediate action.

Use tools like ESLint with security plugins:

Today was a great day, because I got to work on integrating ESLint into our codebase! I'm a funny code monkey. I enjoy good coding practices like linting, user/technical/product documentation, testing, accessibility, and security. These are topics that are usually deprioritized over shipping working code, because code can work without any of the things I listed as my programming passions. But if all those practices are implemented the code will rarely break (or be broken) and is more reliable code. Why not create "reliable working code" from the start?

The commonly used ones in this section are ESLint and Prettier, but there are also some confusion in their usage

There are two tools for that: Prettier and ESLint.

ESLint: Also static analysis

For the linter, I chose ESLINT. I chose it because ESLINT is a very common linter for javascript code, and there's a lot of useful guides on setting it up. Here's the link for ESLINT: https://eslint.org/

ESLint is another VSCode extension and/or npm module that can be used to check for lint warnings and errors live while programming, or with a simple command run. I chose ESLint as I have chosen to have it in react projects in the past and figured it would be easy to start with. The documentation can be found here

ESLint