analytics: Getting 404 for `script.js`
First of all, great work with the updates. Watching the conference was really inspiring. Of course, my first thing to do was to update one of my Next.js projects and try the new goodies.
At one point I decided to try out this new Analytics feature called Audiences, but after adding it to the project I am getting these errors in the console.
After some quick search in the vercel org I came across this repository where I found a reference for this va/script.js file.
Overall, the audiences feature is working, I am getting visitor data in the newly enabled dashboard page; the issue only is that the browser logging this error.
If you need further details, example codes, let me know, but what i did was basically follow your guide:
- install
@vercel/analytics - import and place the
Analyticsreact component into the_app.jsxfile, like this:
import { Analytics } from '@vercel/analytics/react';
import '../styles/globals.css'
const MyApp = ({Component, pageProps }) => {
return (
<>
<Component {...pageProps} />
<Analytics />
</>
);
}
export default MyApp
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 27
- Comments: 57 (4 by maintainers)
We’re actively working on a solution for this issue. We’ll keep you posted!
Hey everyone! We just rolled out the fix for this issue. You will have to redeploy your apps to make it work.
Let us know how it goes 🙌
Found out that mby if you use adblock, that will stop the script.js from running.
Unfortunately, re-deploying my project is not solved the error log in my case.
Same issue with SvelteKit.
Removing
i18nfrom my next.config.js did resolve the issue for me.I think this happens when you integrate the analytics on your project without activating the analytics on Vercel
Okay, it seems like we still have some issues relating to i18n interfering with analytics. We’re working on a fix for sites using i18n now. I believe sites without i18n should work fine though.
+1 - facing the same issue. Some guidance on how best to handle both a 404 page + allowing the analytics package to come through would be great.
I’m also having a similar problem. I don’t get any analytics data on my dashboard though.
I added this to my Gatsby project by adding
injecttogatsby-browser.js, which does its job and adds the script to the<head>. But theva/script.jsgives a 404, which makes sense because there’s no such file anywhere. Is Vercel supposed to intercept and serve this file?I also have rewrites defined in my project so maybe this is overriding the hypothesized intercept. This may be an edge case.
Hi, further update here: we’ve shipped a change that should resolve any issues with
i18ninterference. You’ll need to redeploy (again) to see the changes, but 🤞 this resolves any remaining issues! Let me know if it doesn’t work 😃There seems to be an incompatibility with the
i18nconfiguration innext.config.js.Any updates?
It works now! 🙌
It works with SvelteKit after redeploying! Thank you so much. 🙏🏼
@vacodoceo we just rolled out a fix for i18n, it takes a while until it’s available for everyone! thanks for confirming 🤗
@tobiaslins I just checked again and it’s working. I enabled audiences, redeployed, and it started working. It’s strange because I redeployed a couple of times an hour ago and it didn’t work, and I don’t think enabling audiences was what fixed it.
Anyway, thanks for the support!
I got the analytics to work using the plain HTML approach in my project (didn’t even need to install the NPM package). Thank you!
Happening on our NextJS site hosted on Vercel too. i18n worth more than analytics at the moment so will wait for official fix.
As @max correctly pointed out, the mentioned path
/va/script.jswill become available on your next deployment after you enabled the feature.If you added the package before you enabled the feature, you can trigger a redeployment which has the same effect.
@bogy0 It seems like the error you’re seeing is related to your browser as you already get data. Have you tried disabling all extensions/ad-blockers?
Now it’s working with i18n. Thanks!
Works, thanks! 😃
Works for us too 🙌
Excellent, it works now, thanks for the work
I can confirm that it is now working for my SvelteKit app after I did a redeployment and leaving audiences enabled.
@tobiaslins still having the same error with SvelteKit
Thanks @dglsparsons, just did a re-deploy there (leaving analytics enabled) and same error.
Works for me as well, thanks! As a docs suggestion, I added the inject script to
gatsby-node.jsfor Gatsby, as it seemed like the correct place for it.@tobiaslins Can confirm that it is working now for my Nuxt app (#5). I got another app (SvelteKit) working with a similar method too.
Having the same problem (script 404) on a Next 13 app (still using
/pages) with a custom 404 page. disabled & enabled the feature in the vercel UI again and redeployed, still 404ing. Also not seeing any data in the Audience dashboard which I think is just a side effect. It says “Vercel Analytics is set up, but detected a non-production environment.” on my local though, so it’s at least trying to do something.