NodeJS-Typescript-Yarn : Error: Cannot find module 'd3' - node.js

I'm getting this error and couldn't resolve d3 import . I'm using Typescript#4.0.5 and Yarn
The file Layout.ts (Layout.js) imports d3 which throws an error.
import * as D3 from "d3";
and yarn build
$ yarn build
yarn run v1.22.5
$ tsc && node dist/lib/index.js
internal/modules/cjs/loader.js:834
throw err;
^
Error: Cannot find module 'd3'
Require stack:
- /home/github/my-app/dist/lib/graphs/Layout.js
- /home/github/my-app/dist/lib/index.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:831:15)
at Function.Module._load (internal/modules/cjs/loader.js:687:27)
at Module.require (internal/modules/cjs/loader.js:903:19)
at require (internal/modules/cjs/helpers.js:74:18)
at Object.<anonymous> (/home/github/my-app/dist/lib/graphs/Layout.js:27:25)
at Module._compile (internal/modules/cjs/loader.js:1015:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1035:10)
at Module.load (internal/modules/cjs/loader.js:879:32)
at Function.Module._load (internal/modules/cjs/loader.js:724:14)
at Module.require (internal/modules/cjs/loader.js:903:19) {
code: 'MODULE_NOT_FOUND',
requireStack: [
'/home/github/my-app/dist/lib/graphs/Layout.js',
'/home/github/my-app/dist/lib/index.js'
]
}
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
and my tsconfig,
{
"compileOnSave": true,
"compilerOptions": {
"target": "es2018", /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019', 'ES2020', or 'ESNEXT'. */
"module": "commonjs", /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', 'es2020', or 'ESNext'. */
"lib": ["DOM","dom.iterable","ES2018.AsyncIterable","ES2017.TypedArrays","es2018", "esnext.asynciterable", "ES5", "ES6"], /* Specify library files to be included in the compilation. */
"allowJs": true, /* Allow javascript files to be compiled. */
"declaration": true, /* Generates corresponding '.d.ts' file. */
"declarationMap": true,
"sourceMap": true, /* Generates corresponding '.map' file. */
"outDir": "./dist", /* Redirect output structure to the directory. */
/* Strict Type-Checking Options */
"strict": true, /* Enable all strict type-checking options. */
"types": [
"node", /* Type declaration files to be included in compilation. */
],
"esModuleInterop": true, /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
/* Experimental Options */
"experimentalDecorators": true, /* Enables experimental support for ES7 decorators. */
"emitDecoratorMetadata": true, /* Enables experimental support for emitting type metadata for decorators. */
/* Advanced Options */
//"skipLibCheck": true, /* Skip type checking of declaration files. */
"forceConsistentCasingInFileNames": true /* Disallow inconsistently-cased references to the same file. */
}
}
any help is much appreciated. Thanks in advance.

There is in built in command build in yarn.
All possible options you can find here.
Try yarn install instead

After a few days, gave it a try again, found a solution for adding type d3,
for old versions,
add globals
yarn install typings --global.
search for typings named d3
yarn typings search --name d3
if not exist install it,
yarn typings install d3 --save. //for old versions
yarn add #types/d3. //latest versions
and it worked as expected!

Related

how to setup tsconfig for using with unit-test

I am a newbee in nodejs and typescript, and I have a problem setting up my mocha unit test framework.
I started to develop in a folder with the following folder hierachy:
myproject
src
dist
The paths specified in the tsconfig.json were not correctly resolved, and a friend made me installed ttypescript and the typescript-transform-paths pluggin.
Here is the resulting tsconfig.json :
{
"compilerOptions": {
"target": "es2016", /* Set the JavaScript language version for emitted JavaScript and include compatible library declarations. */
"module": "commonjs", /* Specify what module code is generated. */
"moduleResolution": "node", /* Specify how TypeScript looks up a file from a given module specifier. */
"baseUrl": ".", /* Specify the base directory to resolve non-relative module names. */
"paths": {
"core/*": [
"src/core/*"
],
"model/*": [
"src/model/*"
],
"module/*": [
"src/modules/*"
],
"utils/*": [
"src/utils/*"
],
"client/*":[
"src/client/*"
],
"test/*": [
"test/*"
]
},
"plugins": [
{
"transform": "typescript-transform-paths"
}
],
"sourceMap": true, /* Create source map files for emitted JavaScript files. */
"outDir": "./dist", /* Specify an output folder for all emitted files. */
"esModuleInterop": true, /* Emit additional JavaScript to ease support for importing CommonJS modules. This enables `allowSyntheticDefaultImports` for type compatibility. */
"forceConsistentCasingInFileNames": true, /* Ensure that casing is correct in imports. */
"strict": true, /* Enable all strict type-checking options. */
"strictNullChecks": false, /* When type checking, take into account `null` and `undefined`. */
"strictPropertyInitialization": false, /* Check for class properties that are declared but not set in the constructor. */
"skipLibCheck": true /* Skip type checking all .d.ts files. */
},
"ts-node": {
"transpileOnly": true,
"require": [ "typescript-transform-paths/register" ],
},
"include": ["src/**/*", "test/**/*"],
"exclude": ["node_modules"]
}
Everything works fine for the development.
I want to start unit testing, and add a test folder along side the src folder:
myproject
src
test
dist
I can type my typescript file in the test, but when I run the test with mocha, the paths are not correclty resolved.
I get the following error:
Test
at Function.Module._load (node:internal/modules/cjs/loader:778:27)
at Module.require (node:internal/modules/cjs/loader:1005:19)
at require (node:internal/modules/cjs/helpers:102:18)
Can anyone give me pointer on how to setup my tsconfig file to use correctly the paths in dev and test?
Thanks!

jhipster based nhipster server start error

I am trying to generate Angular NestJS based application using Jhipster i.e, nhipster.
Below is my jhipster and nodejs version numbers:
Jhipster : 7.7.0
NodeJS: 16.14.0 LTS
But I am getting the below error, when I am trying to start the server:
Error:
/projects/nhipster/mauto/server/node_modules/ts-node/src/index.ts:240
return new TSError(diagnosticText, diagnosticCodes)
^
TSError: ⨯ Unable to compile TypeScript:
src/client/header-util.ts:56:19 - error TS2552: Cannot find name 'URL'. Did you mean 'url'?
56 url = new URL('http://localhost' + url);
~~~
src/client/header-util.ts:55:32
55 private static prepareLink(url, pageNumber, pageSize, relType): any {
~~~
'url' is declared here.
at createTSError (/Users/kmadasu/kishore/mnkb/projects/nhipster/mauto/server/node_modules/ts-node/src/index.ts:240:12)
at reportTSError (/Users/kmadasu/kishore/mnkb/projects/nhipster/mauto/server/node_modules/ts-node/src/index.ts:244:19)
at getOutput (/Users/kmadasu/kishore/mnkb/projects/nhipster/mauto/server/node_modules/ts-node/src/index.ts:360:34)
at Object.compile (/Users/kmadasu/kishore/mnkb/projects/nhipster/mauto/server/node_modules/ts-node/src/index.ts:393:11)
at Module.m._compile (/Users/kmadasu/kishore/mnkb/projects/nhipster/mauto/server/node_modules/ts-node/src/index.ts:439:43)
at Module._extensions..js (node:internal/modules/cjs/loader:1155:10)
at Object.require.extensions.<computed> [as .ts] (/Users/kmadasu/kishore/mnkb/projects/nhipster/mauto/server/node_modules/ts-node/src/index.ts:442:12)
at Module.load (node:internal/modules/cjs/loader:981:32)
at Function.Module._load (node:internal/modules/cjs/loader:822:12)
at Module.require (node:internal/modules/cjs/loader:1005:19)
[nodemon] app crashed - waiting for file changes before starting...
That "URL" function at your line "56" is not imported into the typescript module properly. It is a function that comes from dom definition inside the typescript compiler. You could find a way to import it into the header-util class. Another way, and what I'd do is enable "dom" in the compiler options in the ts-config file of the server, by adding "dom" to the lib array like so:
{
"compilerOptions": {
/* Basic Options */
"typeRoots": ["node_modules/#types"],
"target": "ES2017" /* Specify ECMAScript target version: 'ES3' (default),
'ES5', 'ES2015', 'ES2016', 'ES2017','ES2018' or 'ESNEXT'. */,
"module": "commonjs" /* Specify module code generation: 'none', 'commonjs',
'amd', 'system', 'umd', 'es2015', or 'ESNext'. */,
"lib": [
"es6",
"dom" /* <--- here you are */
]
...
}

Built TypeScript application imports from wrong, src instead of dist, folder

TLDR; App builds but tries to import files from src folder instead of dist
I have an Express app that is built with TypeScript.
This is the tsconfig.json
{
"compilerOptions": {
"target": "es5", /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019', 'ES2020', or 'ESNEXT'. */
"module": "commonjs", /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', 'es2020', or 'ESNext'. */
"sourceMap": true, /* Generates corresponding '.map' file. */
"outDir": "dist", /* Redirect output structure to the directory. */
"strict": false, /* Enable all strict type-checking options. */
"noImplicitAny": false, /* Raise error on expressions and declarations with an implied 'any' type. */
"moduleResolution": "node", /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
"baseUrl": "./dist", /* Base directory to resolve non-absolute module names. */
"paths": {
"*": [
"node_modules/*"
]
}, /* A series of entries which re-map imports to lookup locations relative to the 'baseUrl'. */
"esModuleInterop": true, /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
"experimentalDecorators": true, /* Enables experimental support for ES7 decorators. */
"emitDecoratorMetadata": true, /* Enables experimental support for emitting type metadata for decorators. */
"forceConsistentCasingInFileNames": true /* Disallow inconsistently-cased references to the same file. */
},
"include": [
"src/**/*",
"custom.d.ts"
]
}
These are my npm scripts:
"scripts": {
"clean": "rimraf dist/*",
"dev": "nodemon",
"tsc": "tsc",
"start": "node dist/index.js",
"build": "npm-run-all clean tsc",
},
npm run build works fine and all seems nice and dandy, but when I run npm run start I get the following error:
/app/server/src/entity/Category.ts:1
import {Entity, PrimaryGeneratedColumn, Column, ManyToMany, BaseEntity} from "typeorm";
^^^^^^
SyntaxError: Cannot use import statement outside a module
The error seems to be that my build for some reason seems to import from the src-folder and not from the build folder. I have no idea what is wrong, any guiding or ideas are appreciated to help me get further.
Ok, so doing "start": "node build/index.js" results in the above behaviour, however if I do the following on the command line:
cd build
node index.js
It works. So I guess some path is wrong in some module in the application. Will update with more if I find a good way to get this working with NPM scripts.
For anybody else that encounters this problem with Typescript + TypeORM, I encountered it too. The way I solved it was by using __dirname to help resolve paths in my TypeORM config.
For example, instead of doing
const connection: DataSourceOptions = {
...
entities: ['src/entities/*.ts', 'dist/entities/*{.ts,.js}'],
}
I modified it to
const connection: DataSourceOptions = {
...
entities: [`${__dirname}/../../entities/*{.ts,.js}`],
migrations: [`${__dirname}/migrations/*{.ts,.js}`],
}
Hope this helps!

Declaration merging doesn't work with express 4.17.* Request type

I want to add a property to the Request type, so I created a folder #types/express and in this folder I've added file index.d.ts with this content.
namespace Express {
interface Request {
user: number;
}
}
In VSCode the error has gone while I'm referencing to req.user, and it even shows that user is of type number
screenshot that shows that "user" property on the "Request" object is treated right
but when I start the server I see the error that says this:
/home/myself/web/my-server/node_modules/ts-node/src/index.ts:434
return new TSError(diagnosticText, diagnosticCodes)
^
TSError: ⨯ Unable to compile TypeScript:
src/app.ts:46:7 - error TS2339: Property 'user' does not exist on type 'Request<ParamsDictionary, any, any, ParsedQs>'.
46 req.user;
~~~~
at createTSError (/home/myself/web/my-server/node_modules/ts-node/src/index.ts:434:12)
at reportTSError (/home/myself/web/my-server/node_modules/ts-node/src/index.ts:438:19)
at getOutput (/home/myself/web/my-server/node_modules/ts-node/src/index.ts:578:36)
at Object.compile (/home/myself/web/my-server/node_modules/ts-node/src/index.ts:775:32)
at Module.m._compile (/home/myself/web/my-server/node_modules/ts-node/src/index.ts:858:43)
at Module._extensions..js (internal/modules/cjs/loader.js:1220:10)
at Object.require.extensions.<computed> [as .ts] (/home/myself/web/my-server/node_modules/ts-node/src/index.ts:861:12)
at Module.load (internal/modules/cjs/loader.js:1049:32)
at Function.Module._load (internal/modules/cjs/loader.js:937:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:71:12)
I'd appreciate any ideas on how to fix it.
p.s. I have done the same with express-session module and added a counter property into the Session interface, and it works flawlessly
With #types/express installed (#types/express-session is sufficient, too), this should work:
index.d.ts:
declare module '#types/express-serve-static-core' {
interface Request {
user?: User
}
}
The important part is that the declaration merging logic for this is part of #types/express-serve-static-core (see https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/express-serve-static-core/index.d.ts).
After loosing a few brain cells I provide myself with answer.
To fix the issue I had to recreate folder structure that can be found in this issue
https://github.com/microsoft/TypeScript/issues/39581
Then I modified tsconfig.json so its typeRoots would look like this
"typeRoots": [
"src/typings/",
"node_modules/#types/"
]
Then, to augment Request type with my custom types I had to use import expression, so in the end the index.d.ts file would have this inside
declare namespace Express {
export interface Request {
user: import("mongoose").Model<import("./../../models/user").User>;
}
}
tsconfig for the guy in the comments
{
"compilerOptions": {
/* Enable incremental compilation */
"target": "es5" /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017', 'ES2018', 'ES2019', 'ES2020', or 'ESNEXT'. */,
"module": "commonjs" /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', 'es2020', or 'ESNext'. */,
"lib": [
"es6"
] /* Specify library files to be included in the compilation. */,
"allowJs": true /* Allow javascript files to be compiled. */,
/* Concatenate and emit output to single file. */
"outDir": "build" /* Redirect output structure to the directory. */,
"rootDir": "src" /* Specify the root directory of input files. Use to control the output directory structure with --outDir. */,
"strict": true /* Enable all strict type-checking options. */,
"noImplicitAny": true /* Raise error on expressions and declarations with an implied 'any' type. */,
/* List of root folders whose combined content represents the structure of the project at runtime. */
"typeRoots": [
"src/typings/",
"node_modules/#types/"
] /* List of folders to include type definitions from. */,
"esModuleInterop": true /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */,
/* Advanced Options */
"resolveJsonModule": true /* Include modules imported with '.json' extension */,
"skipLibCheck": true /* Skip type checking of declaration files. */,
"forceConsistentCasingInFileNames": true /* Disallow inconsistently-cased references to the same file. */
}
}

Typescript non-relative import with node js and ES modules does not work

I am trying to create a simple Typescript script that uses ES modules, execute it with node and have sourcemaps for debugging.
The script executed with node test.ts:
import foo from './foo'
//import bar from './../src/util/bar' //works
//import bar from 'src/util/bar' // does not work. Linter nor tsc show any warning, but when trying to execute, error says bar can't be found
import bar from '#util/bar' // same as above
console.log('test 0')
console.log(foo + bar)
export {}
foo.ts:
export default "foo_module"
bar.ts is very similar.
Here is tsconfig.json:
{
"compilerOptions": {
"target": "es5", /* Specify ECMAScript target version: 'ES3' (default), 'ES5', 'ES2015', 'ES2016', 'ES2017','ES2018' or 'ESNEXT'. */
"module": "ESNext", /* Specify module code generation: 'none', 'commonjs', 'amd', 'system', 'umd', 'es2015', or 'ESNext'. */
"allowJs": true, /* Allow javascript files to be compiled. */
"jsx": "preserve", /* Specify JSX code generation: 'preserve', 'react-native', or 'react'. */
"sourceMap": true, /* Generates corresponding '.map' file. */
"outDir": "lib", /* Redirect output structure to the directory. */
"moduleResolution": "node", /* Specify module resolution strategy: 'node' (Node.js) or 'classic' (TypeScript pre-1.6). */
"baseUrl": ".", /* Base directory to resolve non-absolute module names. */
"paths": {
"*":[ "./../*" ],
"#util/*":[ "./../src/util/*" ],
}, /* A series of entries which re-map imports to lookup locations relative to the 'baseUrl'. */
"allowSyntheticDefaultImports": true, /* Allow default imports from modules with no default export. This does not affect code emit, just typechecking. */
"esModuleInterop": true /* Enables emit interoperability between CommonJS and ES Modules via creation of namespace objects for all imports. Implies 'allowSyntheticDefaultImports'. */
},
}
When all imports are relative, everything works fine.
When bar.ts is imported using non-relative import (src/util/bar), tsc and linter do not complain, but when trying to execute it with node the following error appears:
internal/modules/esm/default_resolve.js:100
let url = moduleWrapResolve(specifier, parentURL);
^
Error: Cannot find package '#util/bar' imported from <...omitted>\scripts\lib\scripts\test.js
at Loader.resolve [as _resolve] (internal/modules/esm/default_resolve.js:100:13)
at Loader.resolve (internal/modules/esm/loader.js:72:33)
at Loader.getModuleJob (internal/modules/esm/loader.js:156:40)
at ModuleWrap.<anonymous> (internal/modules/esm/module_job.js:42:40)
at link (internal/modules/esm/module_job.js:41:36) {
code: 'ERR_MODULE_NOT_FOUND'
}
Minimal example for reproduction is here
Looks like Typescript does not support converting paths back to relative.
this feels like a Typescript missing feature.

Resources