The main question is about the naming convention:
workers
npm package
@workers
self/workers
@self/workers
There is also one more case - use eslint/tslint to group imports and thus separate something from node_modules from your own stuff.
node_modules
But in any case - this is a must-have feature.
The names you choose depends on the way your project is structured. You can also decide to entirely avoid such names that can cause conflicts. It's entirely up to you and that's why the "@" symbol can help distinguish.
Seems like node "imports" dictate the prefix to be "#".
Are you sure you want to hide this comment? It will become hidden in your post, but will still be visible via the comment's permalink.
Hide child comments as well
Confirm
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The main question is about the naming convention:
workers? Well sounds like anpm packagename. How to distinguish?@workers? Well, actually the same - like a package from an org.self/workersor@self/workers? Scoped but verbose.There is also one more case - use eslint/tslint to group imports and thus separate something from
node_modulesfrom your own stuff.But in any case - this is a must-have feature.
The names you choose depends on the way your project is structured. You can also decide to entirely avoid such names that can cause conflicts. It's entirely up to you and that's why the "@" symbol can help distinguish.
Seems like node "imports" dictate the prefix to be "#".