-
Notifications
You must be signed in to change notification settings - Fork 300
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
New version of fable-library #3614
Comments
This is "normal", currently the only person that can push packages to I opened a ticket to NPM to request transfer of the ownership of They said that such request can take a long time because they need to be careful about ownership transfer. I tried to contact Alfonso by email didn't get an answer either. |
Yeah, I was afraid of this response. |
@nojaf beware of elmish/hmr#44 |
@laurentpayot Fable.Core and Also, I am using Elmish.HMR with latest version of Fable without problem so I need to have a look at how you are using it in your case and what is different. |
🖐️ Oh, I do! But I get what you are saying. What is the latest status of this? If nothing seems to be happening could we consider using a different name maybe? |
|
We found the ONE 😝 (just kidding). I am still waiting an answer from NPM/Github support but I don't think it will happen. We could go with We could go with I personally would prefer to go with a organisation but like that I can make people maintainers for the whole organisation and avoid forgetting to add someone to a package. |
Do you need the fancy |
@nojaf Yes this is how NPM identify an organisation / scopes so yes this is how it is going to be. To give you an exemple of how package will be named: https://www.npmjs.com/search?q=@mangelmaxime |
I see, well I really have a strong preference on the naming here. |
To me, it just convey that is more like something made by the "community" than official Fable itself but that's not a big deal. If I was to have 2 propositions it would be Any of these two would do for me and would unstuck us from the current situation at least. Meaning that we could release |
Description
I noticed there was a new release of
Fable.Core
on NuGet, but there didn't seem to be any release of fable-library on npm.The text was updated successfully, but these errors were encountered: