question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

v3: 400 Bad Request

See original GitHub issue

nuxt 2.15

I upgraded to v3.0.0-0 and ran yarn dev. This immediately errors out:

ERROR 400 Bad Request (https://fonts.googleapis.com/css2?family=DM%2BSans:ital,wght@0,400;0,500;0,700;1,400;1,500;1,700&family=DM%2BSerif%2BText:ital,wght@0,400;1,400&display=swap)

Here’s my config from nuxt.config.js:

    googleFonts: {
      // Download so there's no external dependencies
      download: true,
      // FYI: if you change any of these fonts, you have to add overwriting: true to allow the plugin
      // to re- download
      overwriting: true,
      families: {
        "DM+Sans": {
          wght: [400, 500, 700],
          ital: [400, 500, 700],
        },
        "DM+Serif+Text": {
          wght: [400],
          ital: [400],
        },
      },
    },

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:5 (3 by maintainers)

github_iconTop GitHub Comments

28reactions
bmulhollandcommented, Jul 26, 2022

The issue with the URL is that the “+” is URL encoded into %2B; it shouldn’t be. The docs still say to include this, however: https://google-fonts.nuxtjs.org/options#families

Changing the + to a space in my config fixes the issue, but this is not documented anywhere. If this is one of the “breaking changes,” then it should be included in https://github.com/nuxt-community/google-fonts-module/issues/98

4reactions
gitintheholecommented, Sep 20, 2022

Looked all over for this answer. The flag/note by @bmulholland (thank you!) about it not being documented to use a space instead of a “+” is an issue and impacts both vue 2 and vue 3.

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Fix a 400 Bad Request Error (Causes and Fixes) - Kinsta
The 400 Bad Request error indicates that the server cannot or process the request due to a client error. Read about the common...
Read more >
reCaptcha v3.0 – 400 bad request error - WordPress.org
Since a few months we see There was an error trying to send your message. Please try again later. when trying to send...
Read more >
How to Fix a 400 Bad Request Error: 8 Easy Methods
The 400 bad request error is an HTTP status code that describes an error caused by an invalid request. Thus, the server can't...
Read more >
400 Bad Request when calling V3 API to get Campaign
One of my client getting this error when calling the V3 api to get campaign detail. Can you please let me know 'why...
Read more >
400 Bad Request Error: What It Is and How to Fix It
An in-depth explanation of what a 400 Bad Request Error response code is, ... May 5, 2022 3:28:28 PM | 400 Bad Request...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found