2023年7月7日发(作者：)

vscode下ts-node传⼊cli参数ts-node写ts，启动时习惯在⾥写 "scripts": { "build-ts": "tsc", "start": "ts-node src/", "start:dev": "nodemon", "serve": "node dist/", "test": "mocha --require ts-node/register test/**/*.ts", "build_browser_dev": "browserify ./src/ -o ./static/ -t [ babelify --presets[env]]" },但是当希望启动时传⼊命令⾏参数时，ts-node没法接受命令⾏参数ProgrammaticYou can require

ts-node and register the loader for future requires by using

require('ts-node').register({ /* options */ }). You can also usefile shortcuts -

node -r ts-node/register or

node -r ts-node/register/transpile-only - depending on your : If you need to use advanced CLI arguments (e.g.

--inspect), use them with

node -r ts-node/register instead of the

ts-node CLI.然后给出段不明配置⽂件Visual Studio CodeCreate a new configuration, add

-r ts-node/register to node args and move the

program to the

args list (so VS Code doesn'tlook for

outFiles).{ "type": "node", "request": "launch", "name": "Launch Program", "runtimeArgs": [ "-r", "ts-node/register" ], "args": [ "${workspaceFolder}/" ]}不知该放那⾥，说得不清楚。参考这个，原来是vscode的, ⾃⼰汇总之后这样{ // 使⽤ IntelliSense 了解相关属性。

// 悬停以查看现有属性的描述。 // 欲了解更多信息，请访问: /fwlink/?linkid=830387 "version": "0.2.0", "configurations": [ { "type": "node", "request": "launch", "name": "启动程序", //"program": "${workspaceFolder}", //"preLaunchTask": "tsc: build - ", "outFiles": [ "${workspaceFolder}/dist/**/*.js" ], "runtimeArgs": [ "-r", "ts-node/register", ], "args": [ "${workspaceFolder}", "--config=D:" ] } ]}这个是按F5启动调试时⽤的。如果还是想npm start ⽤参数呢？这样： "scripts": { "build-ts": "tsc", "start": "node -r ts-node/register src/", "start:dev": "nodemon", "serve": "node dist/", "test": "mocha --require ts-node/register test/**/*.ts", "build_browser_dev": "browserify ./src/ -o ./static/ -t [ babelify --presets[env]]" },⽤node -r ts-node/register代替 ts-code然后 nodemon的配置⽂件⾥这样：{ "ignore": ["**/*.", ".git", "node_modules"], "watch": ["src"], "exec": "npm start -- --server=localhost", "ext": "ts js"}--加空格之后 是参数部分。这样ctrl+shift+B启动，start:dev在src/⾥//命令⾏参数('', );可以收到请⽆视现在改回windows下写码。。。主要是sublime text 3 的 ctrl+B运⾏脚本⽅便+中⽂显⽰，然后经常要写其他的⽅案各种杂事，各种办公软件win⽐较⽅便。活在vscode chrome npm pipenv的世界⾥，操作系统之间区别不⼤。将来部署时，在docker⾥启动直接⽤ npm start -- --server=XXX, --config=YYY 即可。

node的⼯程下各种.json的配置⽂件已经不少了。有点雪花式配置的意思。因为不同的组件每个都有⼀个配置⽂件，也算合理。⽽且⽤⽂件配置总⽐⽤gui⼿⼯点击填写⽅便多了。果然到了后端，就充满了cli，配置⽂件。⽤这样的思想组织的npm来管理前端，想想也挺有意思的。不管了，现在配置⽂件写进去了，能⽤就⾏。