Logan, Ut
Showing:

Openbase Activity

Joined Sep 2021

Rating Distribution

5
33
4
9
3
3
2
0
1
0

Feedback Distribution

4
Easy to Use
4
Great Documentation
3
Performant
3
Highly Customizable
3
Bleeding Edge
3
Responsive Maintainers

Top Reviews

fu
@twilio/flex-uiTwilio Flex UI
I've used this library for over a year and a half or more now, because i've been forced to professionally, and my biggest pet peeve is all their stuff is dependent on old dependencies causing us to have to write our entire code base based on old dependencies and old ways of doing things. Leading to a crappier overall codebase on our part as a result--that is not as testable as it could be and that is not nearly as clean as it could otherwise be if we could just simply use all the latest and greatest packages like with any other major npm package. (@twilio/flex-ui finally got early hooks support now but still, 16.13.1 is the latest react version they now support--and it took forever for them to even support it--we actually had to hire them just to figure out we could join their beta program in order to be able to use react hooks before it was officially supported--and even still they don't have beta programs for being able to use the latest version of react-redux and redux hooks for instance. It just makes it so tough when dealing with all the out-dated peerDependency requirements simply because your whole project is reliant on THIS package and THIS package won't even let you build or deploy successfully without adhering to THIS package's old peerDependency requirements) I didn't even know react when I first started and practically every example I found didn't work because, as it turned out--all @twilio/flex-ui's peerDependencies were outdated and I finally figured out I had to go through literally each and every third party package/example we wanted/needed to implement and we had to determine the exact right older version that would actually work right with the latest @twilio/flex-ui version. (The pre-hooks versions of everything at the time) It's just been kind of a nightmare tbh--not to mention a huge security concern. We are expected to develop all this stuff out NOW at my organization--NOT TWO YEARS FROM NOW. Meaning our whole entire codebase will be built out with the OLD STUFF by the time they finally support today's generation of packages--and by then I guarantee you there will be even better/cleaner/newer peerDependency packages out that still will be out of our grasp at the time--therefore the latest and greatest third-party dependencies will seemingly forever be out of reach thanks to THIS package. And so I'm just a little fed up with it all tbh. For instance, right now I'm particularly frustrated because I want to use the latest react-redux hooks way of doing redux instead of relying on coding our whole project out the old react-redux non-hooks way--and I want to use the latest ways of being able to unit test the latest react-redux hooks stuff. (As you may know, redux is notoriously difficult to unit test when you have to unit test it when the whole project is setup the non-hooks redux way) And there's not a single thing we can do about ANY OF IT besides code our whole project out the OLD WAY while meanwhile complaining about how bad it sucks to be continually restricted in this way on sites like this in hopes for change... (Their whole source code is completely private too and their bundles are completely locked down which also sucks--the typings only get you so far at the end of the day) There's definitely room for improvement is all i'm saying.
fu
@twilio/flex-uiTwilio Flex UI
I've used this library for over a year and a half or more now, because i've been forced to professionally, and my biggest pet peeve is all their stuff is dependent on old dependencies causing us to have to write our entire code base based on old dependencies and old ways of doing things. Leading to a crappier overall codebase on our part as a result--that is not as testable as it could be and that is not nearly as clean as it could otherwise be if we could just simply use all the latest and greatest packages like with any other major npm package. (@twilio/flex-ui finally got early hooks support now but still, 16.13.1 is the latest react version they now support--and it took forever for them to even support it--we actually had to hire them just to figure out we could join their beta program in order to be able to use react hooks before it was officially supported--and even still they don't have beta programs for being able to use the latest version of react-redux and redux hooks for instance. It just makes it so tough when dealing with all the out-dated peerDependency requirements simply because your whole project is reliant on THIS package and THIS package won't even let you build or deploy successfully without adhering to THIS package's old peerDependency requirements) I didn't even know react when I first started and practically every example I found didn't work because, as it turned out--all @twilio/flex-ui's peerDependencies were outdated and I finally figured out I had to go through literally each and every third party package/example we wanted/needed to implement and we had to determine the exact right older version that would actually work right with the latest @twilio/flex-ui version. (The pre-hooks versions of everything at the time) It's just been kind of a nightmare tbh--not to mention a huge security concern. We are expected to develop all this stuff out NOW at my organization--NOT TWO YEARS FROM NOW. Meaning our whole entire codebase will be built out with the OLD STUFF by the time they finally support today's generation of packages--and by then I guarantee you there will be even better/cleaner/newer peerDependency packages out that still will be out of our grasp at the time--therefore the latest and greatest third-party dependencies will seemingly forever be out of reach thanks to THIS package. And so I'm just a little fed up with it all tbh. For instance, right now I'm particularly frustrated because I want to use the latest react-redux hooks way of doing redux instead of relying on coding our whole project out the old react-redux non-hooks way--and I want to use the latest ways of being able to unit test the latest react-redux hooks stuff. (As you may know, redux is notoriously difficult to unit test when you have to unit test it when the whole project is setup the non-hooks redux way) And there's not a single thing we can do about ANY OF IT besides code our whole project out the OLD WAY while meanwhile complaining about how bad it sucks to be continually restricted in this way on sites like this in hopes for change... (Their whole source code is completely private too and their bundles are completely locked down which also sucks--the typings only get you so far at the end of the day) There's definitely room for improvement is all i'm saying.
@material-ui/coreMaterial-UI is a simple and customizable component library to build faster, beautiful, and more accessible React applications. Follow your own design system, or start with Material Design.
Overall, I like material-ui for the most part. We use it in our production environment. Sometimes we have issues with the form controls not rendering right, etc. I really like the angular version of material-ui. But have you seen the material-ui store they have alongside this package? If not--you should definitely check it out. They have some examples in their that are some of the cleanest looking themes I've ever seen! And those are all built on this package so I guess I just still have more learning to do in the react realm. We always seem to have problems with rendering these days, either renders too much or too little--that and unit testing react redux stuff. But as for material-ui in particular, they have excellent docs that we've made use of numerous times and I'd recommend it to anyone programming in react!
@angular/materialComponent infrastructure and Material Design components for Angular
This is such an awesome library. It's cool to dig into how they do various things to gleen insight into how you can do some of your own components better. Based on my experiences in using @angular/material in our production environments--@angular/material is really one of the best component library packages out there. It is so well maintained and tested and have you seen their build/docs generation pipeline? It's freakin amazing holy crap. There's so much to learn from these guys it's nuts. I do just want to say that if given the choice, i'd definitely choose @angular/material over material-ui just cuz @angular/material seems to be a lot more reliable/less buggy and you never have to worry about the controls not rendering right, rendering too much, not being testable, etc, etc. Excellent work maintainers!!! 🔥🔥🔥🔥🔥
webpackA bundler for javascript and friends. Packs many modules into a few bundled assets. Code Splitting allows for loading parts of the application on demand. Through "loaders", modules can be CommonJs, AMD, ES6 modules, CSS, Images, JSON, Coffeescript, LESS, ... and your custom stuff.
Webpack is the ultimate build tool. I like gulp a lot as well, i've used both in a professional capacity. But the cool thing about webpack is it's all mostly based on configuration and you don't need a whole directory full of different custom commands to do what you are trying to do--you can do pretty much anything within a single file per environment/configuration--which makes webpack truly hard to beat. In addition, gulp can be used to supplement webpack which is also cool. Those two are by far my two favorite build tools. We use webpack for almost everything these days, a lot of it comes built into other packages these days as well. It seems to me like webpack is winning the race!
jestDelightful JavaScript Testing.
Jest is a great javascript/typescript test runner. Based on my experiences, they do a really good job at like incremental compilation and allowing you or the ide to easily run only like the tests that have changed, one test at a time, etc, etc. I'm still getting used to jest, I'll admit, but I do still think you'd be better off with jest plus a separate dependency injection system like angular has. Yea you can mock imports in jest, but try mocking nested redux higher order components with jest using the module syntax--it's just not fun is all I'm saying and it's hard to get right. At the end of the day tho jest + angular is where it's at in my personal opinion! 🔥
typescriptTypeScript is a superset of JavaScript that compiles to clean JavaScript output.
These days we use typescript for everything--including within our react code. The pros to all the static type checking are huge. It helps a lot if you use it effectively. (i.e. if you don't just type everything as any) I still wish it would be a little more seamless to get everything set up correctly, like with python and django that stuff just works--you don't have to configure the source maps and all that jazz, you are left with a bunch of compiled code to look at, etc. But at the end of the day I'd pick typescript over vanilla javascript any day. They've done a good job with this package.
@nrwl/workspaceSmart, Extensible Build Framework
Based on my experiences, nrwl is truly amazing!! ⭐️⭐️⭐️⭐️⭐️ I love nrwl and how they set you up for success in building out monorepos from the start. I prefer the nrwl workspace to the default angular-cli workspace tbh. For multiple reasons, but just to name a few because nrwl is set up to only build and test what has changed which speeds up your ci/cd pipelines and they also have a generous free tier where they speed up your builds by adding concurrent distributed build capabilities--for free--even when building on your local machine. As I stated, nrwl is truly awesom 🔥🔥🔥🔥🔥
fullcalendarFull-sized drag & drop event calendar
We use this lib for all of our production env calendar requirements pretty much. It really is probably one of the nicest most full featured calendar packages out there from what I have found. It might be getting a little dated at this point, idk, I do know their original implementation was likely based on jquery though. But even still, they are able to port it over to angular and react and I see it everywhere these days in different themes that are for sell, etc, so they must be doing something right! 🌟
eslintFind and fix problems in your JavaScript code.
Eslint is great. It really is such a powerful tool for ensuring your team all codes consistently and in a clean manner. As a team lead--eslint is your best friend--or else it should be. You can configure rules that everyone must follow to make your code more maintainable in the end. I also really like how they are making eslint the de-facto linter for javascript and typescript so that there will be no confusion/incompatibility among the community going forward. Excellent work you guys! ⭐️⭐️⭐️⭐️⭐️
react-hook-form📋 React Hooks for forms validation (Web + React Native)
My experiences with react-hook-form are in a professional capacity. We switched to react-hook-form because we were having problems with too much rendering/re-rendering. It helped out quite a bit with our rendering, and we aren't looking back at this point!

GitHub Activity

Joined Feb 2015
5
Followers
7
Following
297
Repositories
18
Gists
72
Pull Requests
43
Issues
333
Starred
58
Watched

Organizations

RentDynamics
@angular/materialComponent infrastructure and Material Design components for Angular
Great Documentation
Easy to Use
Performant
Highly Customizable
Bleeding Edge
Responsive Maintainers

This is such an awesome library. It's cool to dig into how they do various things to gleen insight into how you can do some of your own components better. Based on my experiences in using @angular/material in our production environments--@angular/material is really one of the best component library packages out there. It is so well maintained and tested and have you seen their build/docs generation pipeline? It's freakin amazing holy crap. There's so much to learn from these guys it's nuts. I do just want to say that if given the choice, i'd definitely choose @angular/material over material-ui just cuz @angular/material seems to be a lot more reliable/less buggy and you never have to worry about the controls not rendering right, rendering too much, not being testable, etc, etc. Excellent work maintainers!!! 🔥🔥🔥🔥🔥


1
20d ago
fullcalendarFull-sized drag & drop event calendar

We use this lib for all of our production env calendar requirements pretty much. It really is probably one of the nicest most full featured calendar packages out there from what I have found. It might be getting a little dated at this point, idk, I do know their original implementation was likely based on jquery though. But even still, they are able to port it over to angular and react and I see it everywhere these days in different themes that are for sell, etc, so they must be doing something right! 🌟


1
20d ago
rxjsA reactive programming library for JavaScript

Rxjs is actually really cool, we use it in all of our angular projects. We started using it in our one react project but since then we've kinda gone away from it in favor of async/await. (We've only gone away from it in our non-angular projects tho) Mainly just cuz our backend doesn't use websockets and async/await is just a lot simpler for simple http calls. But at the end of the day I really like where rxjs has taken the angular community, I love all you can do with rxjs--there's literally nothing you can't do really. I like how they made everything tree-shakeable recently too.


0
20d ago
jestDelightful JavaScript Testing.

Jest is a great javascript/typescript test runner. Based on my experiences, they do a really good job at like incremental compilation and allowing you or the ide to easily run only like the tests that have changed, one test at a time, etc, etc. I'm still getting used to jest, I'll admit, but I do still think you'd be better off with jest plus a separate dependency injection system like angular has. Yea you can mock imports in jest, but try mocking nested redux higher order components with jest using the module syntax--it's just not fun is all I'm saying and it's hard to get right. At the end of the day tho jest + angular is where it's at in my personal opinion! 🔥


1
flex-plugin-scriptsPackages related to building a Twilio Flex Plugin

Flex-plugins is alright. We use it in our twilio flex project. It took me the longest time to figure out exactly what a flex plugin was tbh. At first we thought we needed flex plugins for the webchat for instance. And there was definitely confusion because the webchat also allows you to add/remove/replace components as well. But ultimately I figured out that a flex plugin is really tied to a package.json file. And since then I haven't had too many complaints about the flex-plugins part of flex beyond they keep switching out the build system which makes it hard to keep up with. I wish they'd instead focus on doing things like adding react-redux hooks support.


0
20d ago
momentParse, validate, manipulate, and display dates in javascript.

Moment oh moment--you gotta love dates. I used to really like this library and we used to use it for everything until just recently when I found out that they are actually discontinuing it because it would be too hard to upgrade to make fully tree-shakable and whatnot. So now we're left looking at what other options we have. Date-fns is the clear runner-up I think, although I don't have much experience with that package yet..


0