Drop your company name, svg logo, link to your website, and links to any repos using tsdx. Going to add these to the website.
From just scanning through the GitHub dependents tab, found some notable companies using tsdx...
jaredpalmer
All 35 comments
@react-google-maps/api and dependencies
https://github.com/JustFly1984/react-google-maps-api/tree/master/packages/react-google-maps-api
https://github.com/JustFly1984/react-google-maps-api/tree/master/packages/react-google-maps-api-marker-clusterer
https://github.com/JustFly1984/react-google-maps-api/tree/master/packages/react-google-maps-api-infobox
https://raw.githubusercontent.com/JustFly1984/react-google-maps-api/master/logo.png
JustFly1984
on 11 Sep 2019
Netlify react-netlify-identity-widget, Logos
sw-yx
on 11 Sep 2019
I use it for my latest lib: https://github.com/netzwerg/react-svg-timeline – thanks for making TSDX ✨
netzwerg
on 11 Sep 2019
TSDX helps me creating libs in this github org:
https://github.com/final-state
👍👍👍🙏🙏🙏
liyuanqiu
on 19 Sep 2019
https://github.com/leveluptuts/fresh migrated from Create React Library
stolinski
on 24 Sep 2019
elado
on 25 Sep 2019
whinc
on 29 Sep 2019
@jaredpalmer once again from the govvy world :) ...
http://www.koniaggss.com/
And very shortly: https://www.aphis.usda.gov/aphis/home/
zachariahtimothy
on 2 Oct 2019
Components to integrate Material UI + React Final Form
https://github.com/lookfirst/mui-rff
(work in progress)
(thanks for a helpful tool)
lookfirst
on 18 Oct 2019
Built my first TS project with tsdx, a logging utility.
zcuric
on 30 Oct 2019
Animation Library with Intersection Observer and React Spring :)
https://github.com/alexvcasillas/react-spring-pop
alexvcasillas
on 31 Oct 2019
Using TSDX for my skill tree package beautiful-skill-tree:
andrico1234
on 13 Nov 2019
NoahZinsmeister
on 17 Nov 2019
https://github.com/tasitlabs/tasit-sdk (PR adding tsdx on the way)
pcowgill
on 21 Nov 2019
pomber
on 12 Dec 2019
ambroseus
on 15 Dec 2019
Redux Toolkit:
https://redux-toolkit.js.org
ambroseus
on 15 Dec 2019
Using TSDX for my react library
https://github.com/devianllert/react-essential-tools
devianllert
on 20 Jan 2020
TinaCMS is using it for some packages.
ncphillips
on 3 Feb 2020
petyosi
on 4 Feb 2020
We at blockstack are moving most of our ts packages to it, with a few that have been using it for a while now! Love it -> https://www.dropbox.com/work/Blockstack%20Branding/Blockstack%20Logos/Full/Blockstack?preview=Indigo.svg
aulneau
on 4 Feb 2020
We use it at Contentful. It's awesome, thanks for your work!
suevalov
on 4 Feb 2020
Using it at Powerley
mcansh
on 6 Feb 2020
Using this heavily at Cycle
Repos:
Also using for a couple internal UI libraries :) Thanks for all the hard work!
mattoni
on 7 Feb 2020
I've used TSDX to create my new micro library wrapme.
https://github.com/gamtiq/wrapme
Thank you for the excellent tool!
gamtiq
on 4 Mar 2020
Hey, the upcoming release(v6) of react-toastify is using Tsdx.
Definitely one of the best toolkit, thanks for the hard work 💪!
fkhadra
on 15 Mar 2020
G2.com - for the (personally open sourced) https://github.com/deanius/polyrhythm
deanius
on 17 May 2020
I am using it https://github.com/benbowes/react-responsive-select - great work 💪 !
benbowes
on 23 Aug 2020
Lyon uses it for monorepo projects internally
LXSMNSYC
on 27 Aug 2020
codepunkt
on 10 Sep 2020
I am using it for https://github.com/4lejandrito/react-guitar. Thanks!
4lejandrito
on 12 Sep 2020
Fresh off the press: https://github.com/KATT/envsafe
🔒 Makes sure you don't accidentally deploy apps with missing or invalid environment variables.
KATT
on 17 Sep 2020
@RobJacobson Hey man, investigating this right now.
jaredpalmer
on 9 Oct 2020
politely
more than a bit snarky
@RobJacobson this is what you said:
Is there a solution, or should I just avoid TSDX?
"obviously not". Moving on to other packages. Bye for now.
That comes off as pretty snarky and passive-aggressive to me
utterly unconcerned
utterly hostile
And those come off as personal attacks.
I would look at yourself before pointing at others.
No, your own snarkiness and attacks aren't polite, and neither is commenting on a totally unrelated thread to flame. Neither is filing a duplicate about an issue that is not with TSDX. Neither is not attempting to search or solve it yourself first when the log clearly displays it is not an issue with TSDX.
Your logs clearly state it is an issue with core-js, but you still filed an issue TSDX, and a duplicate at that. It would be a duplicate in core-js as well. As I wrote and as is the norm in most open-source repositories, issues are not a forum for debugging help. That's not unique to TSDX and nor is the error you received.
that's your problem, not mine
As I've already written, TSDX cannot fix an issue with core-js, used by millions of repos (including plenty of the alternatives, if not all of them), which is upstream of upstream of upstream of upstream (literally 4 levels up) and nor can TSDX fix an issue that seems to be with your specific environment. Your environment is, in fact, your problem.
fix the installer
The "installer" is NPM, there is no specific TSDX logic there. NPM is used by virtually all packages.
Saying "just Google it" isn't a valid response.
I didn't just link to a google search, I also linked to 6 upstream issues. And, in fact, the search and those issues offer a variety of solutions... And as I wrote, it's only an error during install, it should still work after install. I'm not sure how none of those are valid if they are, in fact, solutions.
I'm not sure how linking to 6 upstream issues and a search that offer solutions for your particular environment for an issue that is 4 levels upstream (again, not in this repo and not fixable here) is "unconcerned" or "hostile". I dug through core-js's issues _for you_ (and the other issue author), did a search _for you_, and even said it shouldn't impact usage, just install. The issue is 4 levels up -- and the logs directly say where -- but I still responded to your duplicate and still did that for you, for free, in my own unpaid free time.
But I suppose it's your prerogative, that instead of thanking me for taking the time to respond quickly and pointing you to 6 different issues and a search that offer a variety of solutions for free, you can flame in various, unrelated places. That comes off as hostile to me.
agilgur5
on 9 Oct 2020
I am not using TSDX. Your "Quick Start" instructions do not work. When I follow those instructions to the letter, on a new installation of Linux Mint, your installer crashes.
I raised this politely through a bug-report (Issue #897). The response can across as utterly unconcerned and more than a bit snarky. The responder just directed me to another closed issue (Issue #897) that didn't answer the question. He ultimately told me, essentially, to "just Google it."
This comes across as utterly hostile to new users. If new users are following the quick-start instructions letter by letter, and the installer crashes consistently, that respectfully that's your problem, not mine. Just (a) fix the installer or (b) note that a problem exists with the installer and provide a short explanation of how to fix it. Saying "just Google it" isn't a valid response.
I was simply trying to evaluate whether this package is right for me. If I can't get a quick-start example working despite several hours and a bug report, my conclusion is "obviously not." Moving on to other packages. Bye for now.
I've reached out to everyone involved privately, but here is my response to today:
We all need to cool down a bit. Remember, this is an open source community project and not an official paid product. Everyone here is volunteering their time and energy to make life easier for the rest of the TS community. @agilgur5 has done a thankless job of maintaining TSDX and responding to issues with actionable references and solutions like he did here.
@RobJacobson As I stated privately, I understand your frustration and I'm sorry. It sucks when there are cryptic errors like this one. In this situation, though, it isn't an issue with TSDX but with core-js. We simply can't control errors that are multiple levels upstream from our codebase. I wish we could, but we just can't. Regardless, attacking the project and the maintainers isn't constructive.
In general, I think everyone's tone can be less combative and more forgiving--especially with what's going on in the universe right now. I hope that the new CoC (#899) will remind folks of this in the future.
jaredpalmer
on 9 Oct 2020
Related issues
Syynth
·
4Comments
agentofuser
·
3Comments
JasonEtco
·
6Comments
smashercosmo
·
6Comments
seungdols
·
5Comments
Most helpful comment
Lyft
