39 })
40);
41
42app.use(session({ cookie: { secure: false } })); 43app.use(helmet.expectCt({ enforce: false }));
44
45// get a list of all files in the current directory22 ))}
23 </ul>
24 <button>Login</button>
25 <SideBar />26 <a href="javascript:void(0)" target="_blank" rel="noreferrer">
27 FAQs
28 </a>22 ))}
23 </ul>
24 <button>Login</button>
25 <SideBar />26 <a href="javascript:void(0)" target="_blank" rel="noreferrer">
27 FAQs
28 </a> 7 }
8
9 componentDidMount() {
10 findDOMNode(this).scrollIntoView();11 this.state.mode = this.props.userSettings.mode;
12 this.setState({
13 mode: this.props.userSettings.mode, 1import Head from "next/head";
2
3/** next-google-font-display */
4export default Test = () => { 5 return (
6 <Head>
7 <linkVariables that aren't defined, but accessed may throw reference errors at runtime.
NOTE: In browser applications, DeepSource recommends the use of ESModules over regular
text/javascriptscripts. Using variables that are injected by scripts included in an HTML file is currently not supported.
Potential ReferenceErrors may result from misspellings of variable and parameter names, or accidental implicit globals (for example, forgetting the var keyword in a for loop initializer).
Any reference to an undeclared variable causes a warning, unless the variable is explicitly mentioned in a /*global ...*/ comment, or specified in the globals key in the ESLint configuration file.
A common use case for these is if you intentionally use globals that are defined elsewhere (e.g. in a script sourced from HTML).
Bad Practice
const foo = someFunction(); // `someFunction` is not defined
const bar = baz + 1; // 'baz' is undeclared
Recommended
import { someFunction } from 'some-file';
const baz = Math.random();
const foo = someFunction();
const bar = baz + 1;