fix(package.json) : add the exact types file instead of the directory

[axel-andre]

This PR is here to solved the issue #475. This is an quick and easy fix at first proposed by @alexesprit.

This problem is actually pretty annoying when you are using VSCode. By pointing to index.d.ts directly we avoid the issue and it does not make any breaking change.

Again, pretty simple PR tho.

(First contribution ever, do not be afraid to tell me if anything is wrong !)

[OmgImAlexis]

@motdotla what's holding this up from being merged? If it's the tests can they please be re-run as this shouldn't be the cause of the failure.

[Anoesj]

@motdotla Please merge this PR 🙃

[OmgImAlexis]

@motdotla can you please check on this issue. This would help a fair few people and it doesn’t break anything.

[axel-andre]

The CI error is not caused by my single line edit. Is it possible to merge this ? Or at least answer here @motdotla when you have time

[olibooty]

While not an exact solution, I tend to use dotenv as part of a package.json script e.g. nodemon -r dotenv/config. No errors so far 🤷

[sirlancelot]

The bug described in #475 is affecting my project only when I open the file jsconfig.json in VSCode. My project doesn't directly depend on dotenv, it is included by one of my dependencies (@vue/cli-service).

I can confirm that applying this patch (setting types to the exact file instead of the directory) fixed the error.

According to TypeScript's official documentation for publishing, the types property must point to a file.

[OmgImAlexis]

@motdotla can you please check on this issue. It’s been a while since we last pinged you.

[motdotla]

this will be released here: #519