Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Feb 11 09:55
    unwitting closed #24
  • Dec 11 2018 20:56

    Munter on master

    Add jsdoc (compare)

  • Dec 11 2018 03:17

    Munter on master

    Update readme (compare)

  • Dec 11 2018 03:05
    Munter closed #184
  • Dec 11 2018 03:03
    Munter closed #203
  • Dec 11 2018 03:02

    Munter on greenkeeper-postcss-6.0.1

    (compare)

  • Dec 11 2018 03:02
    Munter closed #201
  • Dec 11 2018 03:02

    Munter on greenkeeper-postcss-6.0.0

    (compare)

  • Dec 11 2018 03:02
    Munter closed #191
  • Dec 11 2018 03:02
    Munter closed #210
  • Dec 11 2018 03:02

    Munter on greenkeeper-postcss-5.2.10

    (compare)

  • Dec 11 2018 03:02

    Munter on greenkeeper-node-sass-4.5.3

    (compare)

  • Dec 11 2018 03:02
    Munter closed #197
  • Dec 11 2018 03:02

    Munter on greenkeeper-node-sass-4.5.2

    (compare)

  • Dec 11 2018 03:02
    Munter closed #196
  • Dec 11 2018 03:02
    Munter closed #194
  • Dec 11 2018 03:02

    Munter on greenkeeper-node-sass-4.5.1

    (compare)

  • Dec 11 2018 03:02

    Munter on greenkeeper-node-sass-4.5.0

    (compare)

  • Dec 11 2018 03:02
    Munter closed #193
  • Dec 11 2018 03:02

    Munter on greenkeeper-node-sass-4.4.0

    (compare)

Oskar
@oskarrough
Great, I'll check it out
Peter Müller
@Munter
If you do a live reloading setup I think the best setup is most likely to put file watchers on your source files instead of the fuse mount. I am currently trying to be clever about file watchers inside fusile, but it feels bad and really doesn't cover all the use cases. I might pull that out again at some point. Not really a problem, since watching the source file and triggering an update in the browser will still hit the file on the fuse mount, which will then be recompiled
Oskar
@oskarrough
Well that would be cool. Set up browser-sync myself and reload browser then fusile does the rest?
Peter Müller
@Munter
Pretty much. As soon as the browser knows it needs to reload an asset, that request will eventually hit fusile and complete the circle
Of course, compared to a gulp setup the transpiler work will be done after all the requests have triggered isntead of before. Might give a delay of a few ms extra. Haven't measured that
Dave Jeffery
@davej
Made a start on a middleware version: https://github.com/davej/piggy-in-the-middle
Peter Müller
@Munter
@gustavnikolaj you might want to get in on this
Dave Jeffery
@davej
Would be nice to see if there are modules that could be shared between the two. Tolk is the obvious example but also caching and source file error reporting.
Peter Müller
@Munter
I haven't found a good way to abstract away the cache yet. The error rendering might be possible to pull out into a standalone module
Dave Jeffery
@davej
Yeah, I'll take a look through fusile when I get the chance and see if there are abstractions that can be shared.
Peter Müller
@Munter
My approach to error reporting might seem a bit controversial
Dave Jeffery
@davej
Ha, why is that?
Peter Müller
@Munter
I'm basically destroying any page the asset is included on in order to show a very obvious error message in the browser
It's all just styling of course.
Dave Jeffery
@davej
Like an overlay or something?
Peter Müller
@Munter
I found it highly beneficial in the livereloading case to get instant feedback on errors. And I have a tendency to not look in the dev servers logs all the time
Dave Jeffery
@davej
Yeah, your using the content property that's basically what I was doing
I used a fixed position overlay at the top of the page
(Not in PITM but in the middleware I was working on before)
Peter Müller
@Munter
fusile has wrappers that do the same for js and html
Those should probably be extracted
Dave Jeffery
@davej
Oh right, how does that work for js?
Peter Müller
@Munter
a script injects the same css overlay, but also puts the stack trace, or whatever error is available, in the console
Dave Jeffery
@davej
ok, cool. Doesn't sound too controversial to me.
Obviously not good for production but perfect for dev
Dave Jeffery
@davej
When you say that it outputs the error in console do you mean the node console or the browser console?
Peter Müller
@Munter
Browser console. But it seems I forgot to add that part in. I was sure I did that :)
Dave Jeffery
@davej
Yeah, browser console is what I did too :-)
Peter Müller
@Munter
For fusile it would make sense to also duplicate these in the node console.
Dave Jeffery
@davej
yup for sure
Cool, when I work on the source file syntax error stuff, I'll try and keep it modular and keep fusile in mind
Perhaps we can share the modules then
Peter Müller
@Munter
I'll pull out the js error and html error module snow
Dave Jeffery
@davej
Cool
What do you think about the idea of splitting tolk into separate modules?
Peter Müller
@Munter
That should certainly happen. The only question is which ones. I'm not sure I'm far enough in the process to know what the best abstractions are yet
Dave Jeffery
@davej
Just the wrapper around accord that forwards 'my-file.scss' to the correct compiler, could be a great module by itself.
Gustav Nikolaj
@gustavnikolaj
@Munter thanks for making me aware of the channel :-) I'll read up on it tomorrow. Good night!
Peter Müller
@Munter
That wrapper will likely change when a concept of configuration enters the stage
Dave Jeffery
@davej
I guess that's more stuff in the options object... but the abstraction is the same right?
Peter Müller
@Munter
Possibly, yes
Peter Müller
@Munter
@davej https://www.npmjs.com/package/jserror is out. Had to do a bunch of cleanup on csserror as well to make it work. Going to bed now and will look at htmlerror tomorrow
Dave Jeffery
@davej
Thanks a million!
Thanks for introducing me to unexpected assertion lib too. It's really nice and has a handy plugin for testing middlewares. Been working on adding tests this evening.
G'night
Gustav Nikolaj
@gustavnikolaj
@davej I have a few questions about davej/piggy-in-the-middle - I was thinking about doing something similar - I guess that's why @Munter pinged me here :-) Why did you not just use tolk directly - what is the use case for baby-tolk?