Repository navigation
require.main.require imports do not work #19117
Description
TypeScript Version: 2.6.0-dev.201xxxxx
From: microsoft/vscode#35489 (comment)
Code
const myModule = require.main.require('./file.js')Run go to definition on myModule
Expected behavior:
Goes to defintion of myModule
Actual behavior:
Nothing happens. Looks like we don't understand require.main.require style imports
Activity
[-]require.main.require does not have path intellisense [/-][+]require.main.require imports do not work[/+]mhegazy commentedon Oct 11, 2017
the analysis of module imports in .js files is limited to the known
requirecall.require.mainis not a pattern the compiler looks for. it is also early in the compilation process to know thatrequire.main.requireis an alias torequire.This is currently a design limitation.
weswigham commentedon Oct 11, 2017
Mohamed Hegazy (@mhegazy) Worse yet,
require.main.requireisn't strictly an alias to require - it's a require relative to the package entrypoint... Something we don't currently define.rafaelmaeuer commentedon Jul 24, 2018
I am looking forward to this feature too. Intellisense is not able to understand
require.main.requireas alias forrequire. But this method helps a lot for readability of code when you have files in deeper folder structures.TheColorRed commentedon Jun 1, 2019
I am not sure if this is the same issue, but what I want is to have the types in the current package, but I want the root package to include 'mongodb'.
When I do the following:
I get the following error:
However, the following works, but isn't what I want:
phramos07 commentedon Apr 13, 2020
Apparently
require.main.requireis referencing the Main package of your program, i. e., the entry script. When running with vscode code & debug tool, this package appears to be something else rather than my node js main process, because it fails to find the modulerequireinside themain.