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

next js and typescript project 102

motion, next, react, tailwind-css, fetch
Orji Dominion Ebubennia•390
@dodosebn
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

  • 22-22•100
    @22-22
    Posted 6 months ago

    Hello,

    Congratulations on your solutions! I recently finished the same challenge and got a very useful comment about the api request. I can see you are fetching first from the client to your server, and then fetching again from your server to an external api (I was doing the same). You are doing everything correctly in route.ts but if you need to execute a function on the server you can also use Server Actions. So instead of route.ts, in actions.ts file you can make a fetch POST request to the external api.

    // /app/actions.ts
    "use server";
    
    const externalApiUrl = "https://cleanuri.com/api/v1/shorten";
    
    export async function shorten(url: string) {
      try {
        const externalResponse = await fetch(externalApiUrl, {
          method: "POST",
          headers: {
            "Content-Type": "application/json",
          },
          body: JSON.stringify({ url }),
        });
        const urlsData = await externalResponse.json();
        return urlsData;
      } catch (error) {
        console.error("Error forwarding request:", error);
        return { error: "Failed to fetch data from the external API" };
      }
    }
    

    and instead of making another fetch in your Main component, you can directly call your action:

    "use client";
    
    ...
    
      const [isPending, startTransition] = useTransition();
    
      async function handleSubmit(event: FormEvent<HTMLFormElement>) {
        
        startTransition(() => {
          // Call Server Action
          const result = await shorten(url);
          ...
        });
      }
    
      return (
        <form onSubmit={handleSubmit}>
          <button>{isPending ? "Submitting..." : "Shorten it!"}</button>
        </form>
      );
    }
    

    I was also recommended to use the libs for form validation, react-hook-form or formik, they are very helpful to track everything.

    I hope you'll find it helpful!

    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