Add repository and dependency in package.json

[Eskibear]

See #21

• The entry "repository" must be specified for vsce to resolve absolute links in .md files.
• The package "uuid" has to be explicitly added into dependency.

[kdvolder]

Why does the @types/uuid under devDependencies have a different version than the uuid under dependencies?

[Eskibear]

Why does the @types/uuid under devDependencies have a different version than the uuid under dependencies?

Technically, the versions of the 2 packages are independent.
You know that eventually TS code is compiled into JS code, and @types/uuid just provides TypeScript type definition for the package uuid.
@types/uuid v3.4.3 was published 10 months ago, uuid v3.3.2 was published 2 months ago. Obviously the types are outdated if there's any change of uuid APIs during this period of time.

Yes ideally following the semantic versioning, they are supposed to match. But in fact there are no mechanism to ensure that. See this anwser, unfortunately it's a known issue over the TS community.

devDependencies v.s. dependencies

Packages listed in "devDependencies" will not be packed into the .vsix package, but those in "dependencies" will. So only "dependencies" are available in runtime, that's why uuid should be added there.

Workaround to bypass TS type check

More to say, sometimes you may want to use a third party JS library, but there is only an outdated "@types" package (potential gaps in types definition because of breaking changes) or even no corresponding "@types" package. For example, without install '@types/uuid' , following import statement will cause TS compile error.

import * as uuid from 'uuid';  // the package "@types/uuid" is needed for tsc to compile. 

tsc -p ./

error TS7016: Could not find a declaration file for module 'uuid'. 'C:/Users/yanzh/Work/vscode-spring-boot-dashboard/node_modules/uuid/index.js' implicitly has an 'any' type.
  Try `npm install @types/uuid` if it exists or add a new declaration (.d.ts) file containing `declare module 'uuid';`

Then you might want to add "//@ts-ignore" above the statement, or set "noImplicitAny" to "false" in your "tsconfig.json" file .

Refs:
microsoft/TypeScript#3019
microsoft/TypeScript#15031

[kdvolder]

Thanks for the clarification. I was assuming that the @types package would follow the same versioning as the js package its type describe as that would seem the most logical approach. But now I understand that isn't necessarily the case.

I did understand that uuid needs to be added to dependencies and why. In fact I thought I already did when I adopted that package to generate unique ids for the classpath callbacks. But it looks like I dropped the ball there somehow. Thanks for fixing that packaging issue.

I vote to merge this PR.