Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change module namespace #8

Closed
hueniverse opened this issue Mar 29, 2019 · 4 comments
Closed

Change module namespace #8

hueniverse opened this issue Mar 29, 2019 · 4 comments
Assignees
Labels
Milestone

Comments

@hueniverse
Copy link
Member

@hueniverse hueniverse commented Mar 29, 2019

No description provided.

@hueniverse hueniverse added this to the 1.2.0 milestone Mar 29, 2019
@hueniverse hueniverse self-assigned this Mar 29, 2019
@mcollina

This comment has been minimized.

Copy link
Contributor

@mcollina mcollina commented Mar 29, 2019

Essentially this module will now move in the hapi namespace? I guess this is related to make Hapi sustainable, have you got some details / is this documented somewhere?

I thought this module was thought as an utility for the community, rather than something hapi-specific

@hueniverse

This comment has been minimized.

Copy link
Member Author

@hueniverse hueniverse commented Mar 29, 2019

Expect a blog post next few days, before you start seeing deprecation warnings...

TL;DR everything is moving to a namespace. People will just need to add @hapi/ in front on this and otherwise will see no changes. Nothing prevents you from using @hapi/ module outside of hapi. This is not the first community to move its modules to a namespace.

That said, if it bothers you, feel free to fork and I'll give you npm ownership over the deprecated name. I am not offering that for any other hapi module moving, but in this case, I am willing to make an exception.

@mcollina

This comment has been minimized.

Copy link
Contributor

@mcollina mcollina commented Mar 29, 2019

Expect a blog post next few days, before you start seeing deprecation warnings...

Thanks! I think I understand why you are doing this, 👍. Good idea, it will be a nice way to offer the paid support.

Are Joy and Lab moving as well?

@hueniverse

This comment has been minimized.

Copy link
Member Author

@hueniverse hueniverse commented Mar 30, 2019

This is not really about paid support. It is more about administration logistics and attribution. Everything is moving to a namespace. If it is under the GitHub hapi org, it is moving to the npm org.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.