Ability to define a custom hook name

[jeremypele]

I'm building a bunch of plugin and wanted to namespace them within my company name, the way @angular or @ngx does.

The issue I'm facing is that if I name my plugin @mycompany/core, @mycompany/core.js will not be a valid hook name (nesting issue) and breaks the installation.

I'm adding the ability to define a name property on the hook definition in package.json so we can overwrite the default package name if required. (ex: naming the hook: mycompany-core.js)

[rosen-vladimirov]

🥇

[rosen-vladimirov]

Hey @jeremypele ,
Thanks a lot for your contribution! It's an awesome idea! I'm merging this PR and we'll do our best to release a new version in the next few days.

[jeremypele]

Thanks @rosen-vladimirov that was quick! 🙏