Add vite + remix app to playground to demo ES Module bug

[matt-hernandez]

Changes

This PR adds a Remix + Vite project to the app to demonstrate issue #908 . In order to reproduce that issue, you have to do npm run build and then npm start. This runs the app as if it's in a production environment. The app will crash and produce this output:

> start
> remix-serve ./build/server/index.js

file:///Users/matt.hernandez/Desktop/Projects/posthog-js/playground/remix-vite/build/server/index.js?t=1720462096078.148:7
import { PostHogProvider } from "posthog-js/react/dist/esm/index.js";
         ^^^^^^^^^^^^^^^
SyntaxError: Named export 'PostHogProvider' not found. The requested module 'posthog-js/react/dist/esm/index.js' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'posthog-js/react/dist/esm/index.js';
const { PostHogProvider } = pkg;

    at ModuleJob._instantiate (node:internal/modules/esm/module_job:122:21)
    at ModuleJob.run (node:internal/modules/esm/module_job:188:5)
    at DefaultModuleLoader.import (node:internal/modules/esm/loader:246:24)
    at importModuleDynamicallyWrapper (node:internal/vm/module:428:15)
    at run (/Users/matt.hernandez/Desktop/Projects/posthog-js/playground/remix-vite/node_modules/@remix-run/serve/dist/cli.js:112:15)

This bug is not reproducible when running npm run dev, which is the strangest behavior. It happens when running the app after build and during e2e tests that involve running a built version of the app in Playwright.
...

Checklist

• [ *] Tests for new code (see advice on the tests we use)
• [ *] Accounted for the impact of any changes across different browsers
• [ *] Accounted for backwards compatibility of any changes (no breaking changes in posthog-js!)

[vercel]

@matt-hernandez is attempting to deploy a commit to the PostHog Team on Vercel.

A member of the Team first needs to authorize it.

[pauldambra]

amazing, thank you for spending time on this! 💖

[pauldambra]

sorry @matt-hernandez we had a replay incident this week that has absorbed a lot of my time... all sorted now
i'll pick this up as soon as i can!

[pauldambra]

(did not mean to click close 🤣 there's an indication of the kind of week I've had)

[matt-hernandez]

@pauldambra I know the feeling too well 😆

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[matt-hernandez]

Still watching this

[jacobjohn-transitiv]

Any update on this or quick workaround? This is preventing me from deploying feature flag functionality in our deployed app due to the same issue noted above -

file:///var/task/build/server/nodejs-eyJydW50aW1lIjoibm9kZWpzIn0/index.js:35
import { useFeatureFlagEnabled } from "posthog-js/react/dist/esm/index.js";
         ^^^^^^^^^^^^^^^^^^^^^
SyntaxError: Named export 'useFeatureFlagEnabled' not found. The requested module 'posthog-js/react/dist/esm/index.js' is a CommonJS module, which may not support all module.exports as named exports.

As noted in the original comment, feature flags are working just fine locally with npm run dev but the deployed version does not work

@pauldambra

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[matt-hernandez]

Still watching this

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[matt-hernandez]

Still watching this

[pauldambra]

hey @matt-hernandez i've been unexpectedly out of the office for three weeks so my to-do list is a little unhealthy right now 🙈

haven't forgotten about this though

i don't know if @robbie-c has time to look at this before i do but i'll tag him in case i can nerd snipe him

https://xkcd.com/356/

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[matt-hernandez]

We’ve seen a workaround for this that doesn’t seem unreasonable. I need to implement it to verify it on my end

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week.

[matt-hernandez]

Going to try the workaround today. If it works, I'll add it to this PR