download VS http-proxy

I first started building the app in the browser, using PDF.js and Download.js to take a PDF and edit it, and then download it to your computer.

In short, is there a way to do this with any decently mature wasm targeting frontend framework?

Here's my personal goto:

Find some minimal CSS framework. My preference is Skeleton [0] or Bootstrap [1]. The key is just finding something minimal that works without too much fuss. Personally, I rather have a minimal framework provide 'responsiveness' so I don't have to worry about it but I also want it to get out of the way of anything I do.

Use JQuery [2]. Don't rely on CSS for animations or interactivity. In theory CSS does a lot. In practice it's a nightmare to use and to get it play well with whatever else I'm doing in the page.

Write in "bare" HTML and "vanilla" JavaScript. Don't use a static site generator and don't use a JavaScript framework.

Port in JavaScript libraries as needed. Some of the ones I tend to use are numeric.js [3], downlaod.js [4] and audience-minutes [5]. If you're doing spreadsheet things, maybe there's some JS package out there that will help.

Doing "raw" HTML/"vanilla" JavaScript makes me effectively unhirable but for limited scope side projects where I have full control and want to minimize bit-rot, this is fine.

The point is to create something that's minimal and focuses on functionality. The CSS is just there to make it not look like a Web 1.0 page but otherwise steps out of the way to focus on the actual usage of the application.

For context, here are some projects where I've used this philosophy (all open source, feel free to pilfer): Noixer [6], Resonator Voyant Tarot [7], Boston Train Track (now defunct) [8], CalebHarrington.com (an artist friend) [9], What Is This License [10], HSV Hero [11].

[0] http://getskeleton.com/

[1] https://getbootstrap.com/

[2] https://jquery.com/

[3] https://github.com/sloisel/numeric

[4] https://github.com/rndme/download

[5] https://github.com/berthubert/audience-minutes

[6] https://mechaelephant.com/noixer/

[7] https://abetusk.github.io/ResonatorVoyantTarot/

[8] https://github.com/abetusk/bostontraintrack

[9] https://calebharrington.com/

[10] https://mechaelephant.com/whatisthislicense/

[11] https://mechaelephant.com/hsvhero

Take a look at https://github.com/http-party/node-http-proxy , specifically their .web() helper

I have been tasked with writing a proxy server that takes a clients requests and forwards it to a target server (normal proxy stuff). The client and the target are out of my control. The only change in the client is that the its requests to the proxy server instead of the target. Now, what I need to do is modify the response from target because the client expects it in a certain format and the server responds with a different format. I have a working implementation using http-proxy (https://github.com/http-party/node-http-proxy) that works over HTTP . But I need it to work over HTTPS, I can't make much sense of the documentation and I can't find any additional resources on how HTTPS can be implemented. The client-proxy and proxy-target connection both need to be encrypted(HTTPS). I found solutions using different tools but they mostly seem to be encrypted end to end, so the proxy can't read the response data(I need to be able to modify it). Any ideas on how I can do this?

What you're describing is a proxy server. If you wanted to use Node.js check out https://github.com/http-party/node-http-proxy. Notice that the examples there just forward the req though which potentially has identifying information like cookies, so you'll need to rework to anonymize. Should be straightforward.

There's several ways to have a blog path contain a separate setup from the marketing/product routes.

One is to run a reverse proxy on the root domain to pull in separate routes for various services.

https://github.com/http-party/node-http-proxy

You can do rewrites at the server level for the root domain

Or if the app on the root domain can do the routing for you (have done this before with a Rails app)

Check the documentation of the http-proxy-middleware library (and of the node-http-proxy library, used under-the-hood) to learn how you can manipulate the proxied request & response.

Relevant node-http-proxy issue: https://github.com/http-party/node-http-proxy/issues/230

I'm running Node app in Heroku which is using node-http-proxy, and I've given my Heroku app the domain "example.com"