Use the full relative path when npm publishing (fixes an issue with npm@7 publishing)

[nilzona]

closes #51

[stefanvanherwijnen]

With this PR it does not seem to read the current version for me:

🚀 Let's release package (currently at 0.0.0)

Edit: Actually, this might be an issue with a non existing release on github.
I do get npm errors:

npm ERR! code ENEEDAUTH
npm ERR! need auth This command requires you to be logged in.
npm ERR! need auth You need to authorize this machine using `npm adduser`

I am logged in to npm to I am not sure why it is not authorized.

Edit2:
Solved by adding

  "publishConfig": {
    "registry": "https://registry.npmjs.org/"
  }

to the packages.

[scalvert]

Is this specifically looking at resolving the compatibility issue with npm v7? Just trying to confirm the scope of the problem.

[scalvert]

Reading the referenced issue this seems to be the case. Thanks for this PR. I'll verify this, as I have a package that I ran into this problem with that also needs a publish.

[nilzona]

hey @scalvert. I actually didn't test this with npm < v7 so I can't tell for sure, but from what I can read this is a npm 7 problem as you pointed out and also a npm 6 problem if the folder name was different from the package name (not verified by me though).

[rwjblue]

Thank you @nilzona!