Use npm as publishing registry.

[lukas-schardt]

Closes #20 .

Removed the references to the github package registry.

Still TODO: We need to save the NPM publishing token inside the NPM_TOKEN secret. I don't seem to have enough rights.

[eddyloewen]

@lukas-schardt I'm not a big fan of these editor specific files in here. I would encourage everyone to put these in a global .gitignore on your computer.

[eddyloewen]

@quarkus How should we notify people that are using element-js already? A note in the changelog/release notes should be fine?

[quarkus]

I would just change the readme.md and document that its now possible to install element-js without a .npmrc file ..

[eddyloewen]

What about the other packages? Will we have to move them all over before we can start installing element-js?
It will probably not be possible to install packages with the same namespace from two different registries - right?

[lukas-schardt]

@eddyloewen I don't think so, only if we are updating the element-js version on the other package. The currently existing GitHub Package should still be usable by the other packages.

[eddyloewen]

@eddyloewen I don't think so, only if we are updating the element-js version on the other package. The currently existing GitHub Package should still be usable by the other packages.

Yes that is true! But if we would update element-js further and I wanted to use a newer version it will only be available on the NPM registry. But thats ok! Eventually we will have to move all the other packages to NPM as well. Rather sooner than later!