If I use the canonicalUrl example syntax in vitepress version 1.2.2, an error occurs when building.

[isishome]

Describe the bug

If I use the canonicalUrl example syntax in vitepress version 1.2.2, an error occurs when building.

str.replace is not a function

So, I downgraded to version 1.2.1 and the error did not occur.

Reproduction

install Vitepress v 1.2.2

canonicalUrl example canonical ex

const canonicalUrl = `https://myhome.com/${pageData.relativePath}`.replace(/index\.md$/, '').replace(/\.(md|html)$/, '')
pageData.frontmatter.head ??= []
pageData.frontmatter.head.push(['meta', { property: 'og:title', content: pageData.title }])
pageData.frontmatter.head.push(['meta', { property: 'og:description', content: pageData.description }])
pageData.frontmatter.head.push(['meta', { property: 'og:image', content: 'https://myhome.com/images/og.jpg' }])
pageData.frontmatter.head.push(['meta', { property: 'og:url', content: canonicalUrl }])
pageData.frontmatter.head.push(['link', { rel: 'canonical', href: canonicalUrl }])

npm run docs:build

Expected behavior

failed to build

occur error => str.replace is not a function

System Info

System:
    OS: Windows 10 10.0.19045
    CPU: (12) x64 AMD Ryzen 5 5600X 6-Core Processor
    Memory: 21.07 GB / 31.92 GB
  Binaries:
    Node: 18.18.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.8.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Chromium (124.0.2478.97)
    Internet Explorer: 11.0.19041.4355
  npmPackages:
    vitepress: ^1.2.2 => 1.2.2

Additional context

No response

Validations

• Check if you're on the latest VitePress version.
• Follow our Code of Conduct
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.

[brc-dd]

Please share a reproducible example. Most likely your canonicalUrl variable is undefined in some case. Try wrapping the head.push statement inside a condtion.

[isishome]

Reproduction

The reproduction has been corrected.

Versions prior to v1.2.2 build with the same code without issue.

[brc-dd]

It still is not reproducible.

Please share an example using https://vitepress.new

Like I said, you might have some attribute value that is not a string.

[isishome]

If I run it in developer mode, there is no problem, but if I just run the build, the following error occurs.

If I comment out the canonical syntax, it builds without a problem.

str.replace is not a function TypeError: str.replace is not a function at escapeHtml$1 (file:///D:/Projects/myhome/node_modules/vitepress/dist/node/serve-BwR5EPUJ.js:19945:14) at file:///D:/Projects/myhome/node_modules/vitepress/dist/node/serve-BwR5EPUJ.js:46689:24 at Array.map (<anonymous>) at renderAttrs (file:///D:/Projects/myhome/node_modules/vitepress/dist/node/serve-BwR5EPUJ.js:46687:29) at file:///D:/Projects/myhome/node_modules/vitepress/dist/node/serve-BwR5EPUJ.js:46671:33 at Array.map (<anonymous>) at renderHead (file:///D:/Projects/myhome/node_modules/vitepress/dist/node/serve-BwR5EPUJ.js:46670:10) at renderPage (file:///D:/Projects/myhome/node_modules/vitepress/dist/node/serve-BwR5EPUJ.js:46625:13) at async pMap.concurrency (file:///D:/Projects/myhome/node_modules/vitepress/dist/node/serve-BwR5EPUJ.js:46770:11) at async file:///D:/Projects/myhome/node_modules/vitepress/dist/node/serve-BwR5EPUJ.js:2618:20

[isishome]

I just found the cause, and found that the replace used in the canonicalUrl variable is not the cause, but occurs in pageData.description.

I have a document where the description is written in multiple lines, and I found out that this was causing the problem. If pageData.description is in Array format, no error occurs as it is arbitrarily changed to join to string.
I wonder why the same error didn't occur in previous versions.

[brc-dd]

Previous escape function was more lax and incorrectly serialised such values. pageData.description should always be a string unless you’ve wrong frontmatter. Most likely it wouldn’t have worked correctly with older versions too. Sure they won’t throw error, but the generated html tags will be wrong. Closing as it’s not a bug with VitePress rather wrong content.