Closed makoto closed 6 years ago
I just found ethpm page about the package naming standard
[a-zA-Z][-_a-zA-Z0-9]{0,255}
looks like /
is not acceptable as a package name.
I will actually reopen the issue, as I found out that many projects such as Aragon does use /
as names space https://www.npmjs.com/search?q=aragon
+1 on this, we would like to be able to use a slash if possible as well.
Hello.
We used to name our package as
dnssec-oracle
and was able to load as an artifact at migration. However, it starts failing when we renamed to@ensdomains/dnssec-oracle
to name space our package with organisation name. When I manually copy the files fromnode_modeules/@ensdomains/dnssec-oracle
tonode_modeules/dnssec-oracle
I was able to load it again. Is this something can be fixed or we should not have/
as package name?