by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
James
@aretecode

> interfaces that describe their intentions

# 🎁 features
- 🌐 api
  - 🍭 iteratable
  - πŸ—£ expressive
  - πŸ’† seamless native integration
- πŸ€– transformable
  - πŸ•΅ debuggable
  - πŸ‘£ traversable
  - πŸ—Ί remappable
  - πŸ‘† tap
- 🎼 composable
  - πŸ‘‚ observable
  - πŸ›‚ types & validation
  - πŸ”Œ extend
  - dot-prop
  - shorthand
  - define
  - ❄️ immutable
- 🏭 nestable factories
- ▢️◀️ easy deep merging
- ⚑ performant & tiny `~7kb` _(gzip)_ _300 byte_ snippet available
NPM version
docs
Dependencies
fliphub
BuildStatus
gzip size
fluent
v1 fliplog with .cleaner, .tree, .prettyobj, better .filter, .level, .prettyformat, .fmtobj, .prettyobj, pretty errors, diff match patch, custom loggers, custom text & data formatters, prep for web usage, sprintf wip, colorer, strip, indent, factory, forceEcho, getText, getData, fliphub/fliplog#23
Wout Mertens
@wmertens
I had an idea, to convert apps using debug by creating fliplog/debug (pretty much export default tag => log.tag(tag)) which has the same API. Then with Webpack you can just alias one to the other.
However, turns out there is some formatting API that doesn't seem to be in fliplog, see https://www.npmjs.com/package/debug#formatters . I suppose that could just be ignored? Thoughts?
James
@aretecode
ahh
@wmertens this is in, but not done
Screen Shot 2017-06-15 at 3.31.39 AM.png
@wmertens https://github.com/fliphub/fliplog/blob/master/plugins/text.js code is here if you want to try using it
Wout Mertens
@wmertens
Hmm that's sort of different - but I would be fine with that formatting outputting just the template and parameters for now. It's more about not including a library into a client bundle if I don't have to…
James
@aretecode
@wmertens are you bundling fliplog o.o ?
are you sure what I linked is different? https://github.com/alexei/sprintf.js
Wout Mertens
@wmertens
oh did not infer that :)
James
@aretecode
infer the sprintf part?
Wout Mertens
@wmertens
BTW, what is the browser story? I don't see any docs for that - does it work? Kind of a dealbreaker :-/
yes
doh there's a sprintf right in there
James
@aretecode
definitely deal breaker sorry :-/
fliphub/fliplog#13 fliphub/fliplog#12
I just have to hardwire some dep paths to take the right turns, I'll prioritize it though :+1:
Wout Mertens
@wmertens
I see. #12 seems to be the big one
James
@aretecode
it's mostly just having to make the list of what features use nodejs only features
Wout Mertens
@wmertens
for webpack building, configuring the plugins with DefinePlugin might work
James
@aretecode
oooo nooooo
Wout Mertens
@wmertens
:)
James
@aretecode
definitely not
instead, they would have a browser field
which webpack will use
Wout Mertens
@wmertens
oh cool
James
@aretecode
and from that, it would allow a couple extra paths
that would enable feature groups
so groups of plugins (presets)
kind of like "build your own" with what features you use, when doing a bundle for browser
Wout Mertens
@wmertens
ok, so you require('log/fancy') somewhere and it includes a bunch of cool plugins
James
@aretecode
pretty much yup exactly
because it's optimized for nodejs usage mostly right now, which means it does some things webpack and other bundlers really dislike :-P
Wout Mertens
@wmertens
and require('log/prod') would exclude most things and fall back to json
James
@aretecode
it will have production conditions to use a pre-built version instead of having to change your code to require the production build
Wout Mertens
@wmertens
Well, I'll watch this space :+1: but I'll use it on the node side anyway, I like the api
James
@aretecode
I built this thing called flipshake before
thanks, I strive to make the api solid - though this logger originated for the browser but since I have been doing mostly node work, It went a little too far node only :-P
if I don't get to the browser stuff soon, remind me :-]
Wout Mertens
@wmertens
alright I will :)
James
@aretecode
fluents/chain-able#9
- export more things 
- add magic glob matcher forked from matcher 
- more tests 
- stress tests 
- improved traversal 
- fixed typos / bad spelling 
- decorator support / top-down composable 
- full typescript definitions 
- convoluted crazy rollup typescript buble build script running...
- ...all while keeping the same size :-D
MethodChain, schema support, 90=>96% cov, cache, utils... major refactor...
James
@aretecode
@wmertens made some progress on this
James
@aretecode
converting chalk -> ascii html -> browser fmt strings, creating a build.... <- other stuff here for browser should push soon