In Typescript, direct use of the require syntax in the case of unconfigured error ‘Cannot find name’ require ‘

why
Require is the syntax for node, and the runtime environment is not the Node environment.
plan
1. Install @types/node: NPM I @types/ node-s-d
2. Json :
compilerOptions add an item:

{
    "compilerOptions": {
    	// ...
        "types": ["node"],
        // ...
}

Read More:

• JS error: require is not defined
• Composer require — dev barryvdh / laravel ide helper error resolution
• An error is reported in the compiler require of laravel: installation failed, reversing/ composer.json to its original content.
• Scala Flink Watermarker Error: Static Methods in interface require -target:jvm-1.8
• Error in require.context in vue3 vite
• Idea running Flink program reported an error: static methods in interface require- target:jvm-1.8
• Linux find file text command (find | grep)
• Could not find appears when JDK is configured java.dll Could not find Java se runtime environment problems
• Eclipse can’t open an error: Error:could not find java SE Runtime Environment/Error: could not find java.dll
• Error: could not find java.dll Error: could not find Java se runtime environment solution
• Error reported after moving or copying Vue items: cannot find module ‘xxx‘
• Cannot find module ‘internal / util / types’ appears during gulp build
• NPM- Cannot find module ‘xxxxx’
• Cannot find module ‘lodash’
• Error: Cannot find module ‘process-nextick-args’
• Error: cannot find module ‘node sass’
• Error: cannot find module ‘mongoose’
• Install koa error Cannot find module’internal/fs’
• Node.js Cannot find module ‘mysql’ ‘express’