shopify-app-template-node VS localtunnel

I tried building a sample app using this link https://github.com/Shopify/shopify-app-template-node sometime back. I was able to run the test app and connect with my development store.

Upon some digging and viewing the Shopify app starter (https://github.com/Shopify/shopify-app-template-node/tree/cli_three) that uses Vite + Express, it looks like the answer lies in somehow proxying(?) the frontend to the backend if in development mode, but I haven't been able to crack it.

Building a Shopify App with anything outside React or Rails can be daunting; you’re on your own for the most part. Since I figured it out with my crew using VueJs: we’ve decided to Open Source the template.

I tried the relative path and that didn't work either. I think the issue is that since it's a Shopify app, all routes are behind oauth. My thinking is that I need to host the stylesheet where it is publicly accessible. Then call it in a similar manner to the google drive folder. This is what was used to scaffold the project. Line 91 is the server side code where oauth is checked for every route

Thanks for the response! Let me dive into that. I am using a custom server but it was scaffolded from Shopify's CLI so I would *assume* POST forwarding would be configured. This is a link to server.js.

I'm building a Shopify App scaffolded with the CLI and have issues with routing using the Nextjs router. The standard embedded app implementation does not update the URL so a RoutePropagator component is needed.

Thanks for the resources! The issue was that I was (intentionally) using a branch from the Shopify CLI that removed the use of Next.js. Because Next.js wasn't used, simply putting the remote script in a Public folder wouldn't work. I ended up switching back to the main branch that used Next.js and the script now renders on my development theme :)

link: https://github.com/Shopify/shopify-app-node/pull/661

localtunnel/localtunnel - Written in node. Popular suggestion.

Thanks for the history. I maintain this list[0], and wasn't aware of OG localtunnel, likely because there's a somewhat newer and now more popular project with the same name[1]. You appear to be correct on timing. Here's the earliest commits on GitHub for each of the projects:

OG localtunnel (2010): https://github.com/progrium/localtunnel/tree/fb82920d9d3e538...

Other localtunnel (2012): https://github.com/localtunnel/localtunnel/tree/93d62b9dbb9f...

ngrok (2012): https://github.com/inconshreveable/ngrok/tree/8f4795ecac7f92...

I'll see that OG localtunnel gets added to the list for posterity.

[0]: https://github.com/anderspitman/awesome-tunneling

[1]: https://github.com/localtunnel/localtunnel

These is a very common problem. Luckily, it's been solved already. My go-to tool for this was ngrok or localtunnel. Both of these tools are great, but they didn't fit my needs perfectly.

localtunnel — Expose locally running servers over a tunnel to a public URL. Free hosted version, and open source.

Localtunnel used to be a nice tunnel. It has gone through some enshittification lately.

> tunnel consent page now requires the tunnel creator's public IP in order to access tunnel content

https://github.com/localtunnel/localtunnel/issues/598

There are free non kafkaesque competitors out there.

I recently went through having to tunnel my development environment to setup an oauth2 flow for a rails integration. I found that using https://github.com/localtunnel/localtunnel was a better fit.

I prefer localtunnel: https://github.com/localtunnel/localtunnel

There's also Local Tunnel (http://localtunnel.me)

Not sure if it works combined with ngrok: https://www.npmjs.com/package/localtunnel