question-mark
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.

Proposal: Option to build without linting

See original GitHub issue

Is your proposal related to a problem?

I’m always frustrated when the build command is linting my code and there is no way for me to skip the linting step. My pipeline is lint > test > build. I want to lint before testing because my test files are also linted. With the current setup, linting happens twice.

Describe the solution you’d like

I would like to be able to opt out of linting: "build" : "react-scripts built --no-lint"

Or (even better) have linting separated from the build command so I can remove it. It would appear this way in the default setup: "build": "react-scripts lint && react-scripts build"

The README never mentions that linting will happen within the build step, so this makes the actual process much more visible.

Describe alternatives you’ve considered

Somehow disabling linting by configuration before the build step happens.

Additional context

A related issue was auto-staled without solution: https://github.com/facebook/create-react-app/issues/7078

Issue Analytics

  • State:open
  • Created 4 years ago
  • Reactions:22
  • Comments:10 (5 by maintainers)

github_iconTop GitHub Comments

4reactions
eturinocommented, Nov 6, 2019

There is another scenario that happens to our team quite a lot.

We have a git hook to ensure that all files committed are fine, running prettier and linters.

When we are bugfixing in the browser, sometimes we comment out pieces of code, just to have the browser throw us an error of “you are importing stuff and then not using it”. It makes quick checks way less trivial.

I’d rather have the option to avoid linting on dev build, since we know that we’re not committing offending code, plus we have the linters in our editors.

2reactions
giubandcommented, Dec 9, 2021

@Primajin Opting out of eslint has been added here: https://github.com/facebook/create-react-app/pull/10170 (added in v4.0.2)

Read more comments on GitHub >

github_iconTop Results From Across the Web

Push Options - GitLab Docs
GitLab supports using client-side Git push options to perform various actions at the same ... Only skips branch pipelines and not merge request...
Read more >
Moisture Control Guidance for Building Design, Construction ...
This document was developed by the U.S.. Environmental Protection Agency, Indoor. Environments Division. It provides practical guidance on how to control ...
Read more >
Content Types - ESBuild
This option prevents you from using features which could cause mis-compilation in environments like esbuild where each file is compiled independently without ......
Read more >
Package.json Conventions - ESLint - Pluggable JavaScript Linter
Here is a summary of the proposal in EBNF. name = life-cycle | main ":fix"? target? option* ":watch"? life-cycle = prepare | preinstall...
Read more >
Migrate from TSLint to ESLint - Visual Studio Code
ESLint: Run · Install the ESLint extension. · Create a task via the Tasks: Configure Task command and select npm: lint. · In...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found