Proxied types are not loaded.

[mjbvz]

From @zavr-1 on September 4, 2018 3:46

Issue Type: Bug

When a package loads some modules via another module, their will lack Intellisense and it is not possible to click through to their definition.

VS Code version: Code - Insiders 1.27.0-insider (346018a, 2018-08-24T05:12:36.061Z)
OS version: Darwin x64 15.6.0

System Info

Item	Value
CPUs	Intel(R) Core(TM)2 Duo CPU P7350 @ 2.00GHz (2 x 2000)
GPU Status	2d_canvas: unavailable_software checker_imaging: disabled_off flash_3d: unavailable_software flash_stage3d: unavailable_software flash_stage3d_baseline: unavailable_software gpu_compositing: unavailable_software multiple_raster_threads: disabled_off native_gpu_memory_buffers: unavailable_software rasterization: unavailable_software video_decode: unavailable_software video_encode: unavailable_software webgl: unavailable_off webgl2: unavailable_off
Load (avg)	7, 8, 6
Memory (System)	8.00GB (0.16GB free)
Process Argv	/Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron -psn_0_24582
Screen Reader	no
VM	0%

Extensions (2)

Extension	Author (truncated)	Version
vscode-eslint	dba	1.5.0
code-spell-checker	str	1.6.10

from file A

import { throws, equal } from 'zoroaster/assert'

where zoroaster/assert is a proxy file (only has module.exports = require(./build/assert)) to zoroaster/build/assert which has:

let throws = require('assert-throws'); if (throws && throws.__esModule) throws = throws.default;
const $assert = require('assert');
const $assert_diff = require('assert-diff');



module.exports.assert = $assert
module.exports.equal = $assert.equal
module.exports.ok = $assert.ok
module.exports.deepEqual = $assert_diff.deepEqual
module.exports.throws = throws
//# sourceMappingURL=index.js.map

1. git clone https://github.com/artdecocode/vscode-require-types.git
2. code-insiders vscode-require-types

3. open test/spec/default.js
4. try use throws function, there will be no intellisense. try click through -- it will get to the parent package, but not any further than that.

5. Uncomment // import assertThrows from 'assert-throws' line. Now, throws works fine.

Whenever the proxy in form of zoroaster/assert is removed in favour of zoroaster/build/assert, then things work. I suppose I have to ln the assert rather than use module.exports = require('./build/assert') but it's still a bug.

Copied from original issue: microsoft/vscode#57833

[mjbvz]

The issue appears to be that that require('assert-throws') does not get resolved in ./node_modules/zoroaster/build/assert/index.js.

Adding a d.ts typings for zoroaster should fix this as well

[zavr-1]

I don't like TypeScript, I don't think it solves any problems because JS is a duck typed language and using JSDoc with a proper IDE like VS Code which can understand @ type {import(.)} Type should be enough. The problem however is more here because I found another case where it happened.

ALSO the require('assert-throws') does get resolve properly, if you import it directly via import { throws } from 'zoroaster/build/assert, or when the proxy assert file is lned. I think the problem is that TypeScript parser does not go more than 1 level deep, but I'll double check that.

[mjbvz]

TypeScript powers both VS Code's javascript and typescript intellisense. It is what analyzes jsdocs

I recommend that you try writing d.ts typings for zoroaster. Even if this specific issue is fixed, proper typings will provide a much better experience

[zavr-1]

Thanks but I explained that I will never write a typings file, I am more than happy with JSDoc and not being part of the whole TS movement. Maybe it's hard to understand but there're true JS fans out there. And why do you think it's a much better experience when experience is literally the same when proper JSDoc is written? Like honestly could you give me an example of "better experience"? Before @type {import('.')} Type in JSDoc it might have been true, but not anymore. There's no need to write and publish typings when JS is not for types (apart from auto-completion, which is once again is achieved with JSDoc).

[RyanCavanaugh]

This works fine for me

[zavr-1]

@RyanCavanaugh This is not what it supposed to be showing, the signature of the throws function is different. The problem is quite annoying actually see

In the end when koa-router gets selected it's me clicking with cmd trying to jump to that file, but it does not work. You can try in this repo in example/Session. Or make a project, add @idio/core and try to make a server with it.

import idioCore from '@idio/core'

const Server = async () => {
  const { url } = await idioCore()
  console.log(url)
}

It's dodgy because the type for Application which is just import of koa is showing fine, but for router not, and for middleware is not, because it's imported from another module.

And it also works in the project directory, with the src folder, but the problem starts when the build is done. Therefore there is a need to just return an object with a known type because a constructor was used, but it does not work because the type is not proxied. It works for packages and files without - but not with. If I open the workspace initially with that file open, it will initialise fine, but not when I then close or jump to it. That's the summary.

[zavr-1]

CAN YOU FIX THIS PLEASE IT IS THE MOST ANNOYING BUG EVER

STEPS TO REPRODUCE

1. git clone git@github.com:idiocc/test.git
2. code test
3. Open src/index.js, hover over idio.
4. Click through on idio so that build/index.js opens.
5. Click through on startApp so that build/lib/start-app.js opens.
6. Go up to the heading of the file, try clicking on require('./setup-middleware'). This does not work!!! Types from there are not loaded!

This is VS Code

This is VS Code Insiders

In Code at least I get a Router (without Middleware, but with Application coming up weirdly), in Insiders I don't get neither router nor middleware because of #27302! It's a disaster!

[weswigham]

Am I doing something from your repro wrong?