-
Notifications
You must be signed in to change notification settings - Fork 92
Expand file tree
/
Copy pathfull_lint_output.txt
More file actions
194 lines (182 loc) · 6.75 KB
/
full_lint_output.txt
File metadata and controls
194 lines (182 loc) · 6.75 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
npx : `next lint` is
deprecated and will
be removed in
Next.js 16.
At line:1 char:1
+ npx next lint
--dir app --dir
components --dir lib
--dir services --d
...
+ ~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~~~~~~~~~~~~~~
~~~~~~~~
+ CategoryInfo
: NotSpe
cified: (`next l
int` is ... in N
ext.js 16.:Strin
g) [], RemoteExc
eption
+ FullyQualified
ErrorId : Native
CommandError
For new projects,
use create-next-app
to choose your
preferred linter.
For existing
projects, migrate to
the ESLint CLI:
npx
@next/codemod@canary
next-lint-to-eslint-c
li .
./app/api/auth/login/
route.ts
Error: Parsing
error: '}' expected.
./app/transactions/pa
ge.tsx
178:33 Warning:
Using `<img>` could
result in slower LCP
and higher
bandwidth. Consider
using `<Image />`
from `next/image` or
a custom image
loader to
automatically
optimize images.
This may incur
additional usage or
cost from your
provider. See: https:
//nextjs.org/docs/mes
sages/no-img-element
@next/next/no-img-el
ement
224:60 Error: `"`
can be escaped with
`"`, `“`,
`"`, `”`.
react/no-unescaped-en
tities
224:74 Error: `"`
can be escaped with
`"`, `“`,
`"`, `”`.
react/no-unescaped-en
tities
./components/Bills/Un
paidBillsSection.tsx
33:25 Error:
Missing "key" prop
for element in
iterator
react/jsx-key
./components/Dashboar
d/SavingsByGoalWidget
.tsx
32:58 Error: `'`
can be escaped with
`'`, `‘`,
`'`, `’`.
react/no-unescaped-en
tities
./components/FAQSecti
on.tsx
59:42 Error: `'`
can be escaped with
`'`, `‘`,
`'`, `’`.
react/no-unescaped-en
tities
./components/Financia
lInsightsHeader.tsx
130:17 Warning:
Using `<img>` could
result in slower LCP
and higher
bandwidth. Consider
using `<Image />`
from `next/image` or
a custom image
loader to
automatically
optimize images.
This may incur
additional usage or
cost from your
provider. See: https:
//nextjs.org/docs/mes
sages/no-img-element
@next/next/no-img-el
ement
223:17 Warning:
Using `<img>` could
result in slower LCP
and higher
bandwidth. Consider
using `<Image />`
from `next/image` or
a custom image
loader to
automatically
optimize images.
This may incur
additional usage or
cost from your
provider. See: https:
//nextjs.org/docs/mes
sages/no-img-element
@next/next/no-img-el
ement
./components/Settings
Header.tsx
44:15 Warning:
Using `<img>` could
result in slower LCP
and higher
bandwidth. Consider
using `<Image />`
from `next/image` or
a custom image
loader to
automatically
optimize images.
This may incur
additional usage or
cost from your
provider. See: https:
//nextjs.org/docs/mes
sages/no-img-element
@next/next/no-img-el
ement
./lib/contracts/bill-
payments.ts
84:1 Warning:
Assign object to a
variable before
exporting as module
default import/no-an
onymous-default-expor
t
./lib/contracts/insur
ance.ts
80:1 Warning:
Assign object to a
variable before
exporting as module
default import/no-an
onymous-default-expor
t
info - Need to
disable some ESLint
rules? Learn more
here: https://nextjs.
org/docs/app/api-refe
rence/config/eslint#d
isabling-rules