deno lint for code quality - Step-by-Step Execution

Concept Flow - deno lint for code quality

Write Deno code

↓

Run 'deno lint'

↓

Deno analyzes code

↓

Reports issues or confirms clean

↓

Fix issues if any

↓

Repeat lint until clean

This flow shows how you write code, run 'deno lint' to check it, see reports, fix issues, and repeat until code is clean.

Execution Sample

Deno

console.log('Hello world');

// Run lint
// deno lint

// Output: No issues found or list of warnings/errors

This code logs a message, then running 'deno lint' checks for style or errors and reports results.

Execution Table

Step	Action	Evaluation	Result
1	Run 'deno lint' on file	Checks code style and errors	Starts analysis
2	Detect missing semicolon	Found at line 1	Reports warning: Missing semicolon
3	Detect unused variable	Found at line 3	Reports warning: Unused variable
4	No more issues found	Lint completes	Summary: 2 warnings found
5	Fix issues in code	Add semicolon, remove unused vars	Code updated
6	Run 'deno lint' again	Checks updated code	No issues found, lint passes

💡 Lint stops when all code is checked and reports issues or confirms clean.

Variable Tracker

Variable	Start	After Fix	Final
code	console.log('Hello world')	console.log('Hello world');	console.log('Hello world');
lint_warnings	2 (missing semicolon, unused var)	0	0

Key Moments - 2 Insights

Why does 'deno lint' report a missing semicolon if the code runs fine?

Deno lint checks code style rules, not just errors that stop running. The missing semicolon is a style warning shown in step 2 of the execution_table.

What happens if I ignore lint warnings?

Ignoring warnings means your code may be harder to read or have hidden bugs. The lint tool encourages fixing issues as shown in steps 4 and 5.

Visual Quiz - 3 Questions

Look at the execution table, what issue does 'deno lint' find first?

A Missing semicolon

B Unused variable

C Syntax error

D No issues

💡 Hint

Check step 2 in the execution_table where the first warning is reported.

At which step does 'deno lint' confirm no issues remain?

A Step 4

B Step 6

C Step 3

D Step 1

💡 Hint

Look at the final lint run after fixes in the execution_table.

If you add a new unused variable, how would the lint output change?

A No change, lint ignores unused variables

B Lint reports syntax error

C New warning about unused variable appears

D Lint stops running

💡 Hint

See step 3 where unused variables cause warnings.

Concept Snapshot

deno lint checks your code for style and errors.
Run it with 'deno lint' in your terminal.
It reports warnings like missing semicolons or unused variables.
Fix issues and run again until no warnings remain.
This helps keep code clean and easy to read.

Full Transcript

Deno lint is a tool that checks your code for style problems and possible errors. You write your code, then run 'deno lint' in the terminal. The tool reads your code and reports any issues it finds, like missing semicolons or unused variables. You then fix these issues in your code and run 'deno lint' again. This process repeats until the tool reports no issues, meaning your code is clean and follows good style. This helps you write better, easier-to-read code.

Practice

1. What is the main purpose of running deno lint on your code?

easy

A. To execute the code and show output

B. To find and report code style and potential error issues

C. To compile the code into a binary

D. To install external dependencies automatically

Solution

1. Step 1: Understand what linting means

   Linting is a process that checks code for style and possible mistakes without running it.

2. Step 2: Identify what deno lint does

   deno lint scans your code files and reports style issues or errors to improve code quality.

3. Final Answer:

   To find and report code style and potential error issues -> Option B

4. Quick Check:

   Linting = Find code issues [OK]

Hint: Lint checks code style and errors, not execution or compilation [OK]

Common Mistakes:

• Confusing lint with running or compiling code
• Thinking lint installs dependencies
• Assuming lint fixes all errors automatically

2. Which command correctly runs the linter on all files in the current folder and subfolders?

easy

A. deno lint --fix

B. deno run lint

C. deno lint .

D. deno lint --all

Solution

1. Step 1: Identify the command to lint files

   The command deno lint followed by a path runs lint on that path.

2. Step 2: Understand the meaning of '.' in commands

   Using '.' means current directory and all files inside it recursively.

3. Final Answer:

   deno lint . -> Option C

4. Quick Check:

   Lint current folder = deno lint . [OK]

Hint: Use dot (.) to lint current folder and subfolders [OK]

Common Mistakes:

• Using 'deno run lint' which is invalid
• Assuming '--all' is a valid flag for deno lint
• Confusing '--fix' as a way to run lint only

3. Given this code snippet in example.ts:

const unusedVar = 5;
console.log("Hello Deno!");

What will deno lint example.ts report?

medium

A. Error: unused variable 'unusedVar'

B. Warning: missing semicolon

C. Syntax error on line 1

D. No issues found

Solution

1. Step 1: Analyze the code for lint issues

   The variable unusedVar is declared but never used, which is a common lint warning.

2. Step 2: Understand what deno lint reports

   Deno lint reports unused variables as errors or warnings to improve code quality.

3. Final Answer:

   Error: unused variable 'unusedVar' -> Option A

4. Quick Check:

   Unused variable = lint error [OK]

Hint: Unused variables cause lint errors, check variable usage [OK]

Common Mistakes:

• Thinking no issues appear if code runs
• Confusing lint errors with syntax errors
• Expecting semicolon warnings when not configured

4. You run deno lint and get errors about unused imports. Which fix will resolve this?

medium

A. Ignore the errors and continue running the code

B. Add --fix flag to automatically remove unused imports

C. Rename the imports to different variable names

D. Remove the unused import lines from the code

Solution

1. Step 1: Understand what unused import errors mean

   Unused imports are lines importing modules or variables that are never used in the code.

2. Step 2: Identify the correct fix

   Removing those unused import lines cleans the code and fixes the lint errors. The --fix flag does not always remove imports automatically.

3. Final Answer:

   Remove the unused import lines from the code -> Option D

4. Quick Check:

   Remove unused imports to fix lint errors [OK]

Hint: Delete unused imports manually; --fix may not remove them [OK]

Common Mistakes:

• Assuming --fix always removes unused imports
• Ignoring lint errors thinking code still runs
• Renaming imports without using them

5. You want to automatically fix some lint issues in your project folder. Which command should you run?

hard

A. deno lint --fix ./

B. deno lint --auto-fix ./

C. deno lint fix ./

D. deno lint --correct ./

Solution

1. Step 1: Recall the flag for automatic fixing in deno lint

   The correct flag to fix some lint issues automatically is --fix.

2. Step 2: Confirm the command syntax

   The command deno lint --fix ./ runs lint on the current folder and applies automatic fixes where possible.

3. Final Answer:

   deno lint --fix ./ -> Option A

4. Quick Check:

   Use --fix flag to auto-correct lint issues [OK]

Hint: Use --fix flag with deno lint to auto-correct issues [OK]

Common Mistakes:

• Using incorrect flags like --auto-fix or --correct
• Typing 'deno lint fix' without dashes
• Not specifying the folder or file to lint