Initialized Bower #23
Conversation
|
May I ask why it hasn't been pushed into Bower yet ? This seems like very useful utility |
|
I would have done it myself but I felt it would be better if the repo owner registered the official repo in the Bower registry. Hence the pull request. |
|
Sure, I agree. However it doesn't seem that owner cares about this anymore. Maybe if you would be willing take over the maintenance ? I am at least glad, that Bower can use github repo directly too. |
|
Have you seen the Amplify.js store module? http://amplifyjs.com/api/store/ It might be a better solution since persist-js seems to be growing stale. |
|
That looks great, didn't knew about that. However it doesn't use cookies as the fallback solution. I would like to have that in there. |
|
Ah that is a good point. I think amplify makes it fairly trivial to implement your own storage type but I haven't really looked into it. When I get a spare moment I will take a look at that. Should it prove to be too much of a hassle to extend amplify and jeremydurham doesn't object I would definitely consider assuming maintenance of the project. |
|
Well here we are again after 7 months, @derekbarnhart. Seems that @jeremydurham really lost all interestest in maintaining this and since I didn't found viable alternative yet, it would be really nice to have it in the bower. How are you feeling about it ? |
Just ran bower init so the repo can be used via the bower cli tool.