Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 27 days ago

link-sharing-app

react, react-router, supabase, typescript, react-testing-library
P
toshirokubota•1,320
@toshirokubota
A solution to the Link-sharing app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What challenges did you encounter, and how did you overcome them?

I struggled a bit for drag-and-drop features, as it was working intermittently. It turned out that it did not work with the touch simulation disabled on Firefox.

I was able to integrate Supabase to the backend. I disabled it for the published live site, as I was not sure how to share it without exposing the key. If you can suggest me how, that would be great.

What specific areas of your project would you like help with?

I would like to know how to integrate github/github-pages and Subspace. So I do not want to publish the Subspace key on Github but still have it accessible for the Live version. Would it be possible without some elaborate backend hosting?

Any suggestions/feedbacks are highly appreciated!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•3,430
    @thisisharsh7
    Posted 27 days ago

    Great work on implementing the solution!

    Simple Tips:

    • GitHub Pages can’t hide secrets. Use something like Netlify or Vercel — they let you store keys safely.

    • If you're using Supabase's public (anon) key, it's fine to expose it, as long as you set proper security rules (Row Level Security).

    • Never push your .env file to GitHub — it may contain keys.

    Why Is .env Showing on GitHub?

    Make sure .env is listed in .gitignore.

    If it’s still showing up, you might have added it to Git already. To fix:

    git rm --cached .env
    echo ".env" >> .gitignore
    git commit -m "Remove .env from repo"
    git push
    

    Suggestions

    • Pick either Netlify or Vercel for hosting.

    • Store your Supabase key in their environment settings.

    • Don’t use GitHub Pages if you want to keep secrets hidden.

    Hope this helps. Happy Coding!

    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