Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 4 months ago

Url shortening api landing page

P
zhansayatazhibayeva•640
@zhansayatazhibayeva
A solution to the URL shortening API landing page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sophie•430
    @ippotheboxer
    Posted 4 months ago

    Hi, there seems to be a bug in your url shortening code.

    When I give a link, it says "undefined" on where the shortened link is supposed to show. The copy button also doesn't work. In the console, it says "Failed to load resource: the server responded with a status of 429 ()". Error 429 means too many requests. The Bitly API that you are using, with the free plan, only allows 5 requests to be made per month.

    It would be better to use the cleanURI, the api provided, since it doesn't require an API key or have any limits. However if you tried to do this on the frontend and found this didn't work, this is due to CORS policy: if you create a very simple backend that hits up this API and then have the frontend fetch it, you could get around this error. You could even just ask chatGPT to create it with node and express if you aren't very familiar with how to do this.

    Also, I can still submit a link even if I didn't put a link in. This will inevitably lead to errors no matter what API you use, so I recommend using .trim() method around the input to validate it and check if anything was given, and then you could use regex to check if the link is in a valid format.

    Hope this helps!

    Marked as helpful

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub