'@' instead of '$' about basetag HOT 8 OPEN

I ran into this today:

npm ERR! code EINVALIDPACKAGENAME
npm ERR! Invalid package name "$": name can only contain URL-friendly characters

The workaround, of course, was

rm node_modules/\$
npm install

Voting again for @.

from basetag.

Thanks for the feedback!

Fun fact: The package was called at-base previously and used the @. Unfortunately, node/npm treat it a bit differently and using the @ would delete/move files in actual projects (very weird bug to figure out). But I guess this is somewhat related to the usage of @name/package in npm.

The @ would have been my first choice too. I thought about using the § but that's also strange.

from basetag.

Does the shell variable escaping give you any problems when using basetag?

from basetag.

Does the shell variable escaping give you any problems when using basetag?

No, and yes. I did ls node_modules/$ which, of course, didn't work. More user error than anything.

@ would delete/move files in actual projects

Do you have any more details on that? I've submitted patches to npm before and I might look into it... someday.

from basetag.

Got it!

I've been thinking about a customizable basetag symbol for v2. Could be done via an optional package.json attribute or .basetagrc or similar. Users could use the default or customize to whatever.

Should be a super simple feature, I'll test it out over the next days and see if there's an issue with @...

from basetag.

@coolaj86

Do you have any more details on that? I've submitted patches to npm before and I might look into it... someday.

See https://gist.github.com/branneman/8048520#gistcomment-3009096 for some (scarce) details.

from basetag.

Good catch! Maybe this was the issue I though I was having with @.

I will do some investigating and think of a solution (maybe combined with #18 )

from basetag.

Damn 😬

You can try to use @ for a project (that you have backed up somewhere). Last time I tried, npm started deleting random folders in my local project. I think this is due to @ being used in GitHub username handling e.g. import from @janniks/basetag. If you find @ to work — great! But I'm not sure it will from a technical standpoint.

Otherwise, we might need to switch to - . _ ~ ( ) ' ! * : , ; — not great 🙃

from basetag.