We were trying to check the page's resource list and noticed that the newer (after 0.11.3 i think) versions throw errors when calling resources.toString.
I've submitted a very simple fix here, and a new spec for resources. We'd love to get this into master so we don't have to refer to our own fork of the project.
I'm new to coffee and vows. Hopefully, the structure of the new spec is acceptable.
* fix resources toString so it doesn't raise errors
* add tests
* trying version change to trigger update in npm client installs
[Closes #228] This patch fixes the fact that Resources toString throw…