Skip to content
New issue

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

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

Already on GitHub? # to your account

Should we archive the repository ? #146

Open
mklabs opened this issue Apr 15, 2022 · 2 comments
Open

Should we archive the repository ? #146

mklabs opened this issue Apr 15, 2022 · 2 comments
Labels

Comments

@mklabs
Copy link
Owner

mklabs commented Apr 15, 2022

Hello @elwayman02 (or everyone else reading me here :)) what do you think ?

Should we archive the repo and recommend using more modern and maintained solutions such as Browsersync.

Are you still using tiny-lr ? I know I'm not (same for my other npm packages really). I'm all in game development as of today.

The other solutions would be to fully transfer ownership of both repo and npm package.

@sly7-7
Copy link

sly7-7 commented Apr 15, 2022

I know ember-cli still rely on tiny-lr. 🤔 @elwayman02 I think you are an "ember" guy, so maybe you have some thoughts about it ?
cc/ @rwjblue, kindly ping, maybe you could be interrested ?

@elwayman02
Copy link
Collaborator

I've raised this question with some of the ember-cli folks on Discord to see what their perspective is.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants