edlaver

/// <reference lib="WebWorker" />

// Based on: https://github.com/jacob-ebey/remix-pwa/blob/main/app/entry.worker.ts
//// Uses a modified version of: https://github.com/dumbmatter/promise-worker-bi (updated to work with service workers)
//// Co-ordinates with the client to fetch session tokens, and redirect if reauth required.
//// Parts taken from: ./web/frontend/hooks/useAuthenticatedFetch.js in the default node template

import { json } from "@remix-run/server-runtime";
import { getUnixTime, add } from "date-fns";
import { PWBWorker } from "../libs/promise-serviceworker-bi";

edlaver

Trigger.dev is "The open source Background Jobs framework for TypeScript".

It allows you to "Create long-running Jobs directly in your codebase with features like API integrations, webhooks, scheduling and delays."

It has support for frameworks such as Next.js, Express, and Remix. But can it work with Gadget? 🤔

Turns out the answer is "Yes", and it works great!

---

edlaver

import React from "react";

import {
  Layout,
  LegacyCard,
  Page,
  SkeletonBodyText,
  SkeletonDisplayText,
  TextContainer,
} from "@shopify/polaris";

edlaver

module.exports = async ({ api, record, params, logger, connections }) => {
  const metafieldNamespace = "<Your metafield namespace>";
  const metafieldKey = "<Your metafield key>";
  const metafieldType = "json"  
  const metafieldOwnerId = `gid://shopify/Shop/${record.id}`; // `record.id` here is the ID of our `shop` record
  const gadgetFieldName = "<The matching field name in your gadget record, e.g. myMetafield>";

  // Check if record change includes our metafield data
  if (record.changed(gadgetFieldName)) {
    logger.info(