Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
up-for-grabs.net
This is a list of projects which have curated tasks specifically for new contributors. These issues are a great way to get started with a project, or to help share the load of working on open source projects. Jump in!
-
-
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
Talkr
Talkr is the lightest i18n provider for React applications. It supports Typescript, provides autocompletion, has 0 dependencies, and is very easy to use.
The project is on early stages (6 months old) and any contributions are welcome. The codebase is fresh, documentation is good, it's easy to get started (no magic things to configure). Project has backlog of features and components which are planned to release in next minor and major versions. From my side: I will review your Pull request and make sure that the code is nothing less than perfect. If you are interested, see contributing guidelines and open a discussion on Github with features/components you want to implement.
Maybe PouchDB.
I'm currently sorting out a few rough edges and will be launching it in a few days. If you have a minute look it up on https://github.com/LiveDuo/destack. There's also an online editor on https://destack-page.vercel.app/.
Many people feel like "I'm not good enough for this project." The problem is people get the impression that project existed with final form. It can be difficult to dive into a project that has been developed over the years. You should spend weeks to understad that code repository. My practical suggestion is find a active small library like a map plugin. Build project. Look at all files try to understand them. When you get the pattern look at issues tab try to solve one of them. Here is an example only 335 line, weekly npm 8000+ https://github.com/brunob/leaflet.fullscreen/blob/master/Control.FullScreen.js
I have created an organisation on GitHub called jsenv to share what I have learnt about JS. For this reason my readmes are going into more details than usual readmes (at least I tried). If you are interested I recommend you to check https://github.com/jsenv/jsenv-core, it is meant to start JS projects from scratch for "beginners". Feel free to contact me if you are interested by what you see 😊
I feel the same and I am really sad when I read such code: most of the knowledge is lost into code that is hard to follow. It took me years (around 10) to find my code style and be confident with it. In the end, I put most of my effort to produce readable code. If you feel adventurous I would recommend to check https://github.com/jsenv/jsenv-inspect. It's a small and simple project. Maybe you can find interesting patterns inside the source code :) I would be interested to get your feedback.
Im working on a visual coding tool: https://github.com/ajthinking/data-story would love to get some help
Hi, if you are looking to work on a open source project, you may make Talkr (a i18n lib) available on React-Native. It already works with next.js and react. The challenge is: no dependencies, only vanilla js/jsx. https://github.com/DoneDeal0/Talkr