search

webtides / element-js

Simple and lightweight base classes for web components with a beautiful API
MIT License
28 stars 3 forks source link

Use npm as publishing registry. #24

Closed lukas-schardt closed 3 years ago

lukas-schardt commented 3 years ago

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 commented 3 years ago

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 commented 3 years ago

@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 commented 3 years ago

@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!