Next.js Discord

Discord Forum

Quotation marks removed by Vercel

Answered
robin posted this in #help-forum
Open in Discord
(using Typescript & Tailwind)
This is more of a Vercel issue rather than a Next one, so I hope this is the right place to put it; when I try to deploy my website to Vercel, I get an error.

Within my tailwind config file, there are some opacity values. I forgot the quotation marks around these values, meaning that they were interpreted as a number type. This gave me an error, as only string types are allowed there.

Fine, that's an easy fix, so I change the number to a string type by adding quotation marks around the numbers.

After committing this change to my main branch though, there doesn't seem to be any change within Vercel. In GitHub, I can confirm that there are definitely quotation marks around my values. However, Vercel still gives me the same issue. Inspecting the Source in Vercel also shows that it hasn't copied over the new quotation marks.

Does anyone know how I can "force refresh" my Vercel deployment? It did recognize that new commits were made, and tried to redeploy after I committed, but it didn't seem to recognize the changes

My code in GitHub:
keyframes: {
        overlayShow: {
          from: { opacity: "0" },
          to: { opacity: "1" },
        },
        contentShow: {
          from: {
            opacity: "0",
            transform: "translate(-50%, -48%) scale(0.96)",
          },
          to: { 
            opacity: "1", 
            transform: "translate(-50%, -50%) scale(1)" 
          },
        },
      },


My code in Vercel Source:
keyframes: {
        overlayShow: {
          from: { opacity: 0 },
          to: { opacity: 1 },
        },
        contentShow: {
          from: { opacity: 0, transform: 'translate(-50%, -48%) scale(0.96)' },
          to: { opacity: 1, transform: 'translate(-50%, -50%) scale(1)' },
        },
      },


TL;DR - Added quotation marks in a TS file to fix a bug, Vercel seems to ignore it, seemingly using the old version and still giving me the bug
Answered by robin
Seems like somehow Vercel just fixed it after a day of no activity. Assuming it must have been some kind of cache that was refreshed or something. Either way, marking this as solved as the problem seems to have solved itself :necoarcthumbsup:
View full answer

1 Reply

Seems like somehow Vercel just fixed it after a day of no activity. Assuming it must have been some kind of cache that was refreshed or something. Either way, marking this as solved as the problem seems to have solved itself :necoarcthumbsup:
Answer