I'm working on documentation today. I'll set up an official copy of this. Once I've done that I'll work on incorporating your fixes, too. Thanks for them!
It would make sense for me to own the npm package I guess. I'll need to figure that out... On Sun, Oct 29, 2017 at 10:36 PM, <[email protected]> wrote: > Hi Anthony, > > I've found a couple of bugs with the polyfill. > > I uploaded your original and applied fixes to this gist. > > https://gist.github.com/damoclark/9a43d8c405d4c72e2325bdabd80496f0 > > I am also wondering whether you wish to maintain an authoritative version > of the polyfill as a repo under the greasemonkey github.com account. If > people wish to adapt it, or otherwise enhance the polyfill, they can create > a fork, but otherwise there will be a known 'goto' spot to find it. > Thoughts? > > I also use npm/browserify as part of my toolset for building user scripts > (for more substantial ones anyway). I've created an npm module version of > the polyfill for my userscripts. I was going to publish via npm, but > wanted to check with you first Anthony to see whether you wish to publish > under the Greasemonkey name. > > Damo. > > -- > You received this message because you are subscribed to the Google Groups > "greasemonkey-users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/greasemonkey-users. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "greasemonkey-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/greasemonkey-users. For more options, visit https://groups.google.com/d/optout.
