ts-node-dev不会在自动重新加载中应用更改

时间:2020-05-29 18:47:30

标签: typescript nodemon feathersjs ts-node

我已经在Typescript中使用FeathersJS构建了一个应用程序,但是尽管typescript的nodemon(ts-node-dev)表示在更改Typescript文件时服务器已重新启动,但更改未应用。 我总是需要终止该应用程序,然后重新开始以查看更改。

这是日志:

[INFO] 15:43:51 Restarting: C:\api\src\models\favorites.model.ts has been modified
Using ts-node version 7.0.1, typescript version 3.9.3
info: Feathers application started on http://localhost:3030

这是package.json上的dev脚本:

ts-node-dev --no-notify src/

这是tsconfig.json:

{
  "compilerOptions": {
    "target": "es2018",
    "module": "commonjs",
    "outDir": "./lib",
    "rootDir": "./src",
    "strict": true,
    "esModuleInterop": true
  },
  "exclude": [
    "test"
  ]
}

这是package.json:

{
  "homepage": "",
  "private": true,
  "main": "src",
  "keywords": [
    "feathers"
  ],
  "contributors": [],
  "bugs": {},
  "directories": {
    "lib": "src",
    "test": "test/",
    "config": "config/"
  },
  "engines": {
    "node": "^12.0.0",
    "npm": ">= 3.0.0"
  },
  "scripts": {
    "test": "npm run compile && npm run mocha",
    "dev": "ts-node-dev --no-notify src/",
    "start": "npm run compile && node lib/",
    "mocha": "ts-mocha \"test/**/*.ts\" --recursive --exit",
    "compile": "shx rm -rf lib/ && tsc"
  },
  "prettier":{
    "singleQuote": true
  },
  "standard": {
    "env": [
      "mocha"
    ],
    "ignore": []
  },
  "types": "lib/",
  "dependencies": {
    "@feathersjs/authentication": "^4.5.3",
    "@feathersjs/authentication-local": "^4.5.4",
    "@feathersjs/authentication-oauth": "^4.5.4",
    "@feathersjs/configuration": "^4.5.3",
    "@feathersjs/errors": "^4.5.3",
    "@feathersjs/express": "^4.5.4",
    "@feathersjs/feathers": "^4.5.3",
    "@feathersjs/transport-commons": "^4.5.3",
    "compression": "^1.7.4",
    "cors": "^2.8.5",
    "feathers-mongoose": "^8.3.0",
    "helmet": "^3.22.0",
    "mongodb-core": "^3.2.7",
    "mongoose": "^5.9.16",
    "serve-favicon": "^2.5.0",
    "winston": "^3.2.1"
  },
  "devDependencies": {
    "@types/compression": "^1.7.0",
    "@types/cors": "^2.8.6",
    "@types/helmet": "0.0.47",
    "@types/jsonwebtoken": "^8.5.0",
    "@types/mocha": "^7.0.2",
    "@types/mongoose": "^5.7.21",
    "@types/serve-favicon": "^2.5.0",
    "axios": "^0.19.2",
    "mocha": "^7.2.0",
    "nodemon": "^2.0.4",
    "shx": "^0.3.2",
    "ts-mocha": "^7.0.0",
    "ts-node-dev": "^1.0.0-pre.44",
    "tslint": "^6.1.2",
    "typescript": "^3.9.3"
  }
}

3 个答案:

答案 0 :(得分:2)

您需要告诉编译器注意更改。添加以下脚本或使用监视标记调整您的compile脚本:

"watch-ts": "tsc -w"

"compile": "shx rm -rf lib/ && tsc -w"

我仔细查看了您的脚本,在我看来,您应该从已编译文件(我猜它们在lib文件夹中)启动服务器。如果是这样,则用于运行服务器的脚本应为:

"dev": "ts-node-dev --no-notify lib/server.js"

您需要在两个单独的终端标签中运行:

npm run compile

npm run dev

答案 1 :(得分:2)

ionut-t的回答是一个可行的解决方法,但是问题是一个很好的解决方案,但没有给出答案。该解决方案实际上绕过了ts-node的{​​{1}}方面,而只是将其用于重新加载,而错过了ts-node-dev的全部好处。恕我直言,ts-node-dev可能出了点问题,或者feathersjs是如何即用型配置的,我想它很快就会以一种或另一种方式解决(如果尚未解决)。

更新:

我是对的...升级ts-node-dev后,它现在可以在单个终端中完美运行。

升级: ts-node-dev

  • 损坏的版本为 1.0.0-pre.44
  • 我使用的固定版本为 1.0.0-pre.50

答案 2 :(得分:0)

--exit-child 添加到 npm dev 脚本似乎对我有用。

"dev": "ts-node-dev --no-notify --exit-child src/",

https://stackoverflow.com/a/62447944/541281