[WIP] separate packagize code into separate dep, pkgize#282
[WIP] separate packagize code into separate dep, pkgize#282ashleygwilliams wants to merge 1 commit intomasterfrom
Conversation
|
@ashleygwilliams Can you please remind me of the reasoning behind this, again? Is it to keep the "npm-ish" stuff out of marky so marky can stick to being a GitHub-style markdown parser? If so, do you think cdn.js should be extracted as well? |
|
oh, also re: |
|
@revin - exactly. i'd like marky to be just a GFM parser, and right now it's doing some other stuff. in the long run- i'm not sure the website wants it to do this stuff and so in preparation, i'm separating it out. i think ideally it's code that we can just get rid of all together. |
|
this is waiting on me moving over the tests. also needs a rebase as this point. |
fixes #257
pulls packagize code into it's own pkg,
pkgize: https://www.npmjs.com/package/pkgizehad to pull
token-utilintopkgize... should we make that it's own separate pkg? i dont like the repeated code but also don't know if we'll even save pkgize so maybe it doesn't matter?