It's all just styling of course.
I used a fixed position overlay at the top of the page
(Not in PITM but in the middleware I was working on before)
Those should probably be extracted
Obviously not good for production but perfect for dev
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
What do you think about the idea of splitting tolk into separate modules?
@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
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
@davej The second question is why you chose to make it ES6 only? Unfortunately, I'm in a position where most of the work I do is still on node 0.10. As far as I can tell, you only really use arrow functions and classes - you even have a promise library already :-)
@gustavnikolaj: 1. See here: Munter/tolk#17, hopefully PITM and tolk can share the same module to do compilation. I think that might look something like baby-tolk which does less stuff than tolk. Feature-wise the differences are no css auto-prefixing and source maps are passed up the promise chain rather than being inlined.
@gustavnikolaj: 2. I just wanted to play with some of the new ES6 stuff, I might convert it back to ES5 later. The promise library is only used to promisify built-in node functions. Native promises are used by the lib. There's also a couple of other things used like ES6 array methods.
I'm a little disappointed to learn that Fuse does not exist on Windows. Or that I use Windows at work. Actually, a little of both. But I might try it out in a Docker instance.