1.27.0: netlify host with tracker script name environment variable

[duboiss]

Since v1.27.0, my custom tracker script name is not available on Netlify but still works on Heroku.
Its the same repository with the same environments variables.

Without env variable, everything work well with umami.js file (which always seems to be accessible, even with the environment variable).

https://portfolio-unami.herokuapp.com/statistics.js
https://unami.duboiss.fr/statistics.js

I think its related to #731 & #977

[mikecao]

I'm not that familiar with Netlify, but I'm guessing it can't run the new Next.js middleware, which is how the tracker script name is handled. We may need to come up with a static solution for Netlify.

[duboiss]

One question, if I rollback to v1.26.0 for testing purposes, will I have database problems? If the v1.17.0 has updated the schema. Thanks

[mikecao]

No schema changes were made.

[AFilthyLeaf]

I have the same issue as this but on Heroku! Not sure what could be causing it.

[christopherpickering]

I did a few prints to try and debug as well. I set the env variable to "something_cool".

Modified function:

Netlify logs:

And when running locally with npm run dev

But when I check the network logs on the netlify build, it looks like it tries to get the umami.js properly. But somehow returns 404 instead of 200.

I wonder if the href of the url object needs to be updated as well? I'll test it out.

[christopherpickering]

I opened an issue w/ netlify, but I have a feeling it is something with dev vs prod in next... as the netlify cli runs fine.
opennextjs/opennextjs-netlify#1266

[christopherpickering]

I'm wondering now if this is something w/ nextjs in the prod vs dev mode on how it handles 404's?https://stackoverflow.com/questions/66854788/getting-404-when-loading-dynamic-routes-on-nextjs