-
Notifications
You must be signed in to change notification settings - Fork 29
improve package visibility #30
Comments
It might be a good idea to change the install instructions on http://node-swig.github.io/swig-templates/ until this is resolved... |
I thought this project was completely abandoned and was looking for other alternatives until I checked one more time and followed the original repo's fork history. Definitely need to have a better way for people to find this new community project. |
Has anyone talked with Paul? I can reach out to him and check NPM rules for abandoned packages... |
For reference, here's the NPM disputes page. |
we're probably getting ahead of ourselves with that. no, i don't think anyone has reached out recently. the 3-4 of us who have done some continued work in this project haven't gone to great lengths to re-request name rights. in regards to @ecoleman's remark about updating the docs, great point. filing it as a separate issue, #32 |
Well finally im here, so we need create content with swig-templates instead "swig" alone, ill try todo some tutorials :D for SEO tracking |
First thing you should do is make clear that there are no breaking changes in updating from swig 1.4.2 to swig-templates 2.0.2. This is not made clear anywhere, I can only guess this is the case from the small comment in the CHANGELOG. If this is confirmed you should definitely add this as the first thing on the README to show everybody that they can just switch the package in their dependencies. |
it's hard to find this package! googling it, even with a bunch of keywords, still gets you to paul's original project.
swig
npm packages to point to our community packagei know paul has demonstrated some reluctance to let go of the reigns. getting his help here would be a big step in realization that the project is alive and kickin'
The text was updated successfully, but these errors were encountered: