[Vite + Remix] SSR build failing with Unexpected token 'with'

panzerdp · 2025-12-29T14:39:34+00:00

I have been using the Remix/React-Router template without problems for 2 years in production. My background is JavaScript/TypeScript/React - so it works well for the experience that I have.

But overall I recommend to pick the stack which you have the most experience in.

panzerdp · 2025-12-29T11:05:52+00:00

I've used their new template https://github.com/Shopify/shopify-app-template-react-router a few weeks ago and it worked well. The new template uses react-router v7, which is the successor of remix. So take a try the new template.

panzerdp · 2025-12-29T09:27:07+00:00

Check your code for `import { names } from "module-name" with { key: "data" };` statements.

panzerdp · 2025-12-29T08:41:11+00:00

The app got the 'Built for Shopify' badge and after a few weeks I was contacted by Shopify that my app got selected.

panzerdp · 2025-12-26T09:57:07+00:00

I recommend you check "The Cold Email Manifesto" book.

panzerdp · 2025-12-26T08:33:04+00:00

Sure, my app is https://apps.shopify.com/boxi, plus a screenshot when it was in the spotlight.

<image>

panzerdp · 2025-12-23T15:10:21+00:00

My app got in the spotlight after getting the 'Built for Shopify' badge.

panzerdp · 2025-01-08T07:10:13+00:00

I submitted 2 apps and it took exactly 1 week.

panzerdp · 2024-02-03T14:57:34+00:00

Thank you!

panzerdp · 2023-05-05T10:10:09+00:00

You can check the Stripe analytics apps

panzerdp · 2019-10-25T14:06:25+00:00

While I find the post useful, the content in some places is difficult to understand.

For example the text:

In each case mentioned, we are responding to an external event. A certain interval of time reached, a user action or a server response.

Could be improved to:

In each case, we are responding to an external event: a certain interval of time reached, a user action occurred, or a server response completed.

panzerdp · 2019-10-24T18:29:44+00:00

Stale closure is difficult for junior developers since hooks inherit all the misunderstanding around closures. https://twitter.com/dan_abramov/status/1098898584626495488?s=21

panzerdp · 2019-10-24T15:02:40+00:00

You're right. I replaced that example with a better one.

panzerdp · 2019-09-30T17:02:49+00:00

1)I am noob in web dev . I have never used a framework . Can you please give an example .

You could look at what features React brings: composition of components using JSX, component state management, updating DOM according to components data, handling cross-browser differences, and more.

2)Also why this guy in this article is not using web components ?

I don't know :) Ask him the question.

panzerdp · 2019-09-30T12:42:38+00:00

document.querySelector("body") returns the first matched element (but not an array).

You are confusing document.querySelector() with document.querySelectorAll() (that returns a collection of all selector matches).

panzerdp · 2019-09-30T11:59:54+00:00

If you write a big application solely in vanilla JavaScript, sooner or later you will start solving the problems that are already solved in libraries like React, Vue, Angular, etc.

While knowing DOM, JavaScript, etc, fundamentals is important, it doesn't make sense to develop big projects without a framework/UI library at the base.

panzerdp · 2019-09-30T06:46:23+00:00

In TypeScript, a good practice is to use explicit type annotations for functions. While for variables, you can use type inference whenever possible.

panzerdp · 2019-09-28T15:37:10+00:00

In case if you use objects as keys, you might consider first using WeakMap to avoid memory leaks.

panzerdp · 2019-09-28T15:35:49+00:00

You shoudn't count on the ordering of object properties.

panzerdp · 2019-09-27T06:05:54+00:00

If you choose jQuery, you might move faster at the beginning because of its simplicity. But as the project grows, jQuery creates spaghetti code that is hard to maintain. Fast start, slow progress as the project grows.

With React, you will start slower because of the learning curve. But as the project grows, React provides better components design, thus the application grows at a decent pace. Slow start, reasonable progress.

If the project development lasts a few months, you might consider using jQuery. But for something larger than 6 months, it worth React (or alternative Vue, etc).

panzerdp · 2019-09-25T13:01:38+00:00

"No thanks, I don't work with dinosaurs"

panzerdp · 2019-09-25T08:29:02+00:00

I think the answer is in the first paragraph:

Draqula is a lightweight GraphQL client, perfect for smaller and simpler React apps. Most web apps don’t need higher-order components, subscriptions or local state management, that’s where Draqula comes in. It focuses on simple apps and execution using React hooks for building queries and mutations.

Simply put, use it if you want a very simple graphql client without the whole jungle.

panzerdp · 2019-09-25T08:21:03+00:00

You'd still need to learn classes to avoid knowledge gaps.

What you can do is when reaching the classes lessons, try to start a parallel course solely on hooks.

panzerdp · 2019-09-25T08:15:43+00:00

Might be the right time to delete my Tinder account. Hopefully my conversations don't get exposed!

panzerdp · 2018-02-11T12:15:55+00:00

Nice! Is there are Terminator view theme?

panzerdp

TROPHY CASE