issue with npm link of ember-cli on windows.

[stefanpenner]

version ends up being undefined for ember-cli all the time. Might something to do with symlinks/junctions on windows?

[rwjblue]

It's possible, I'll update my ievms and try to repro locally.

[stefanpenner]

@rwjblue i'll try tonight/tomorrow to debug this. I have a good local reproduction, just tired so i figured I would leave a reminder issue :)

[rwjblue]

Curious if this is still an issue.

[suchitadoshi1987]

@rwjblue @stefanpenner I am having the same issue. I am running yarn link and .exists() always returns undefined

[stefanpenner]

@suchitadoshi1987 are you sure? This issue I believe is windows specific. Do you have a reproduction handy?

[MrChocolatine]

I am not sure it's 100 % related to the same issue but I am also getting undefined when checking the version property of a package.

I was trying to work on this PR:
typed-ember/ember-cli-typescript#1142

And as we can see in the original PR, the author left a note:

Seems like somehow VersionChecker isn't getting the dependencies in the ember-cli-blueprint-test-helpers context 🤔

I am also getting the same error.

I tried to dig into this and it turns out, for some reason I don't understand, the following function resolvePackagePath returns null for the package ember-data (while it is correctly detected in the dependencies of the project):

ember-cli-version-checker/src/dependency-version-checker.js

Line 41 in 513e0d2

this._jsonPath = resolvePackagePath(this.name, basedir);

Because this._jsonPath is set to null, the following if() that are supposed to set this._version are not entered and the property stays undefined.