Brand Request: TypeScript

[magnus-trent]

It would be nice to have an icon for TypeScript, Microsoft's superset of Javascript. General usage I couldn't say much past the fact that I personally use the icon on information pages when talking about what tools I use for projects.

Thank you.

[lundyio]

bump

[DevidCIC]

The addition of TypeScript would be very nice.

[alexandre-delaloy]

Yeah, TypeScript is very used actually, it would be very nice to add it !

[abarnwell]

+1

[adhiravishankar]

+1

[OliveCh12]

Typescript icon still not updated ?

[alevasseurEG]

+1

[super-bunny]

+1

[emanuelescarabattoli]

+1

[admarko]

+1

[theusoliveira]

Please add this icon! I really need it!

[alexandre-delaloy]

After more than 2 years, no response from the Font Awesome team for this icon, and the dev icons in general.

Anyway, I'm using Devicon from @konpa.

[ghost]

LETS GET THIS TO THE TOP OF THE LEADER BOARD

[ariel-frischer]

Bump

[RuMont]

bump

[thfrod]

2025 and still no ts logo :/

[naterfute]

Mfw still waiting for the logo 🥹

[oardi]

+1

[RuMont]

7 years to create a TS icon means they definitely wont do it. Unsubscribing from this issue.
I drop this here in case somebody needs it:

https://www.svgrepo.com/vectors/typescript/

[MohammadAliJa]

7 years to create a TS icon means they definitely wont do it. Unsubscribing from this issue. I drop this here in case somebody needs it:

https://www.svgrepo.com/vectors/typescript/

I think they need an extra 7 years to be completed, 😕.

[DJFriar]

Adding another comment to hopefully bump this request up. Especially odd it is missing considering their documentation even includes instructions on how to support TypeScript.

[kuraykaraaslan]

Hi Font Awesome team,

It’s been over 13 years since TypeScript became a mainstream language and yet there is still no official Font Awesome icon for it. TypeScript is now a first-class language across both frontend and backend ecosystems — supported directly by major frameworks like React, Angular, Vue, and even Node.js itself.

To help move this forward, here is a fully functional and styled icon definition based on the existing visual identity of TypeScript:

const customTSIcon: IconDefinition = { prefix: "fab", iconName: "typescript", icon: [ 32, 32, [], "f0c8", "M0 16v16h32v-32h-32zM25.786 14.724c0.813 0.203 1.432 0.568 2.005 1.156 0.292 0.312 0.729 0.885 0.766 1.026 0.010 0.042-1.38 0.974-2.224 1.495-0.031 0.021-0.156-0.109-0.292-0.313-0.411-0.599-0.844-0.859-1.505-0.906-0.969-0.063-1.594 0.443-1.589 1.292-0.005 0.208 0.042 0.417 0.135 0.599 0.214 0.443 0.615 0.708 1.854 1.245 2.292 0.984 3.271 1.635 3.88 2.557 0.682 1.031 0.833 2.677 0.375 3.906-0.51 1.328-1.771 2.234-3.542 2.531-0.547 0.099-1.849 0.083-2.438-0.026-1.286-0.229-2.505-0.865-3.255-1.698-0.297-0.323-0.87-1.172-0.833-1.229 0.016-0.021 0.146-0.104 0.292-0.188s0.682-0.396 1.188-0.688l0.922-0.536 0.193 0.286c0.271 0.411 0.859 0.974 1.214 1.161 1.021 0.542 2.422 0.464 3.115-0.156 0.281-0.234 0.438-0.594 0.417-0.958 0-0.37-0.047-0.536-0.24-0.813-0.25-0.354-0.755-0.656-2.198-1.281-1.651-0.714-2.365-1.151-3.010-1.854-0.406-0.464-0.708-1.010-0.88-1.599-0.12-0.453-0.151-1.589-0.057-2.042 0.339-1.599 1.547-2.708 3.281-3.036 0.563-0.109 1.875-0.068 2.427 0.068zM18.276 16.063l0.010 1.307h-4.167v11.839h-2.948v-11.839h-4.161v-1.281c0-0.714 0.016-1.307 0.036-1.323 0.016-0.021 2.547-0.031 5.62-0.026l5.594 0.016z" ], };

[nolway]

Maybe one day...

[omarhurani]

can we at least get a reason on why this isn't being done?

[lai-bianca]

It would be very useful to have this icon! I see that this was self-assigned recently, so I hope that means that this is actually going to be added.

[sensibleworld]

So... our backlog of brand requests has reached a point where even we can't pretend we're keeping up. Some of these issues were opened before I had gray hair. And I've had gray hair for a LONG time. On top of that, treating requests as issues has always made it way too hard to see the forest for the trees.

To fix this, we are now managing all brand requests in GitHub Discussions. No more +1s or thumbs-ups needed. There's an upvote system built-in.

We are closing existing brand requests as part of this transition, but we are not saying no to your request.

If this brand request is still relevant for you, please re-open it in Discussions (and feel free to include a link back to this issue):
-> https://github.com/FortAwesome/Font-Awesome/discussions/new?category=brand-requests

And listen. We know this is annoying. If you need to vent, here are some pre-written responses you can use when opening the new discussion:

• Cool cool cool. No worry at all. I love re-requesting a brand that's redesigned three times while this issue was open.
• If an issue closes after seven years and nobody responds, did it ever really exist?
• I see you have chosen violence today. Re-opening per instructions.
• What's next? I have to file a TPS report, too?
• I am filled with the fury of a thousand suns. Why do I have to re-open the discussion? Couldn't you have just bulk converted all of the issues to discussions? What? You couldn't? What do you mean Github removed that feature earlier this year? You'd have to manually click the "convert to discussion" button on thousands of issues, while also ensuring it gets added to the correct category? That's a bunch of bull-phooey.
• No biggie.

[sensibleworld]

Hey folks! This is in progress. It'll be in our next release.

[kuraykaraaslan]

I literally added the code above… just copy and paste this. I mean, how hard can it be?

[jabronus]

I literally added the code above… just copy and paste this. I mean, how hard can it be?

As Jory mentioned, this is already ready for our next release 🙂

[sensibleworld]

Added in 7.2: https://fontawesome.com/icons/typescript?f=brands&s=solid