Closed BrunnerLivio closed 6 years ago
Thanks for the quick fix. I look forward to the release containing it :)
It looks like v3.0.2 was tagged but not published to npm. Could you please publish it? Thank you!
@mathiasbynens oh I actually forgot I’ve published this repo on npm. I thought you’d only need the output data. Sure, I’ll publish the new version, as soon I’m home. I’ve went on a spontanous holiday trip to Munich, Germany, so won’t be able to publish it until saturday. I can ask if my friend can lend his laptop for short, if it is urgent, don’t want to block you. :)
—-
I’m really curious for what you need this as a npm package, not just only the outputted *.json data? Is your implementation open source?
Edit: Forgot to logoff with my second account. I’m @BrunnerLivio
@mathiasbynens 3.0.2 is now up
I’m really curious for what you need this as a npm package, not just only the outputted *.json data?
I'm consuming the generated JSON data and would like to version it just like other dependencies in my code, i.e. by relying on npm and package.json
.
Before
See issue #2
Changes
output
Changes the name "Farfetchd" to "Farfetch'd"output
Changes the name "Mr Mime" to "Mr. Mime"core
AddstemplateId
forComponentSetttings
.Component
s withtemplateId
only gets called with items which have the settemplateId
.processing
Add MrMime componentprocessing
Add Farfetchd component