What is rootDir? rootDir is set to a root folder, that contains all your source files. If not specified, TS will automatically choose a suitable parent folder of all inputs. rootDir also determines the output directory. What does the error mean? My guess is you have an import statement for logging.ts somewhere in notifier-server: import … Read more
The answer comes from @DenisPshenov’s comment in one of the answers. It’s buried, so I’ll provide it here… Tell Node where the base url is with NODE_PATH environment variable so that it can resolve absolute paths: Linux / macOS NODE_PATH=dist/ node ./dist/index.js Windows Powershell $env:NODE_PATH=”dist/” node ./dist/index.js
dir *.ts /b /s > ts-files.txt tsc @ts-files.txt del ts-files.txt This will compile all *.ts files in working directory and its sub directories. If you don’t want to include sub directories, just remove the /s part from the first line. Note that you can also add other arguments to the tsc line. Here is what … Read more
If you’re using tsc as a node module, make sure you’ve installed it with npm install -g typescript Then it should be available globally in your node command prompt
The main difference is that tsc transpile all the file according to your tsconfig. Instead, ts-node will start from the entry file and transpile the file step by step through the tree based on the import/export.
TL;DR Just write export {} in the outermost scope of your files. At some point there needs to be a semantic disambiguation for whether a file should be treated as a module (and have its own scope) or a script (and share the global scope with other scripts). In the browser, this is easy – … Read more
I faced the same issue. I tried many things and now i got a solution which works for me. I have an app and a library in my angular project. I want to use a library alias in my app. I have following structure: ├── projects │ └── lib │ └── src │ └── lib … Read more
I had a similar problem when initially converting to a TypeScript project. I also set resolveJsonModule: true and the src directory was copied to the output dist directory. The underlying reason is that one of my source files required package.json at the root of the project. Once I removed that, tsc no longer added src … Read more
When you pass in files for compilation with tsc src/index.ts, your tsconfig.json is ignored. From the documentation: When input files are specified on the command line, tsconfig.json files are ignored. Your npm build script should just be tsc without passing any files.
I think what you want is something like this (my current setup): “scripts”: { “compile”: “tsc && node app.js”, “dev”: “./node_modules/nodemon/bin/nodemon.js -e ts –exec \”npm run compile\”” } I created two scripts “compile” and “dev”. To start developing you simply run npm run dev which starts nodemon and makes it watch .ts files (using the … Read more