paluh

Following `pscid` `package.json` and `.npmignore` I've created dirty experimental publish workflow which works fine: https://github.com/paluh/literate-purescript/commit/cc8c02d07fa93e245ef835f803a9d2d7ff852500 I'm not sure if this is the most beautiful approach as it adds `index.js` into...

P.S. So `npm install paluh-litps` then `paluh-litps --help` works fine.

@Thimoteus It seems to be maintainable as `pscid` is long standing project already. 1. Should I provide a PR with this solution? 2. Would you be so kind and publish...

@Thimoteus I don't want to bother you but maybe you can find a moment and consider answering above two questions ;-)

Do we really need to provide `pathInfo` as a separate field? As @JordanMartinez pointed out users like me who use _routing duplex_ or _boomerang_ want full path and query string...

It is somewhat related so I want to point out that for example query parsing is context dependent which can be somewhat surprising. It can depend whether a backend expects...

I fully agree with @JordanMartinez. We can provide utils for quick and opinionated parsing but this should be an opt-in in some way. P.S. I've also updated library links in...

To have mutating request we should start from a builder I think. It could be something like `Builder Unit Request`. To avoid copying at all we create a builder in...

@Woody88 just showed me that he is starting from something like `Builder {} Request` in his prototype . And I fully agree that it is better (because the API is...

You can have local .vimrc in project directory with `let g:psc_ide_server_port = PORT_NUMBER` which I'm using extensively. I think that random port can be used, but only when `psc_ide_server_port` is...