Replies: 5 comments 4 replies
-
facing the same issue, do you got any workaround for this or still the same? |
Beta Was this translation helpful? Give feedback.
-
what is interesting is that it appears when the app is deployed on the vps. locally I don't see that $ sign rendered. I ensured that the env is production both locally and on the vps and yes locally I don't see it rendered |
Beta Was this translation helpful? Give feedback.
-
may i know the cpu architecture for the vps that you guys are using? i am using arm but it didnt happen when i am deploying on my another vps using x86 architecture |
Beta Was this translation helpful? Give feedback.
-
~# uname -m I am also using cloudflare for domain set up so as OP said this most likely have to do with cloudflare doing something because locally I don't see that $ sign. mind that the app is dockerized |
Beta Was this translation helpful? Give feedback.
-
this is my current workaround, changed defer from cloudflare script to async, it work and i still got the web analytics eventho it does not show the web analytics are on inside the cloudflare https://github.com/Hazqeel09/getdoav3/blob/main/remix/app/root.tsx |
Beta Was this translation helpful? Give feedback.
-
When I turn on Cloudflare Web Analytics, Cloudflare injects a script which I suppose the following function is not expecting, because when it executes, a
$
is appended to my body on every page:Here's a reference to the start of the page load:
Cloudflare's script is injected above the
<template>
. This has the idB:0
, which means this is what$RC()
will immediately look for (see its first argument).Whilst this function is being executed, it eventually reaches the final
for(; b.firstChild; )
loop.a
is some text ("\n"
), and the rest do not matter becausea
does not change. Once the loop breaks, it goes intoa
.a
is just some text whose parent element is<body>
. Now, it just doesa.data = "$"
and a dollar symbol is now at the bottom of the body on every page.The issue here is that
a
for some reason is just some text. It seemsa
should instead be a comment node, as it looks like some hydration comment shenanigans are taking place.Using the following dependencies:
Needless to say, this will not occur during development. This problem is alleviated with Web Analytics turned off, but I'd rather have it on. So, whose issue is this? React's? Remix's? Not sure where to go from here.
Beta Was this translation helpful? Give feedback.
All reactions