The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning. Learn more →
Fullstack-starterkit Alternatives
Similar projects and alternatives to fullstack-starterkit
-
Prisma
Next-generation ORM for Node.js & TypeScript | PostgreSQL, MySQL, MariaDB, SQL Server, SQLite, MongoDB and CockroachDB
-
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.
-
webiny-js
Open-source serverless enterprise CMS. Includes a headless CMS, page builder, form builder, and file manager. Easy to customize and expand. Deploys to AWS.
-
devhub
TweetDeck for GitHub - Filter Issues, Activities & Notifications - Web, Mobile & Desktop with 99% code sharing between them (by devhubapp)
-
graphql-code-generator
A tool for generating code based on a GraphQL schema and GraphQL operations (query/mutation/subscription), with flexible support for custom plugins.
-
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.
-
Server-Driven-UI
A framework example for Server Driven UI (SDUI) that teaches you the best practices to scale.
fullstack-starterkit reviews and mentions
-
Javascript: Why does this repo have a package.json file in the root directory in addition to the frontend and backend directories?
I'm learning fullstack JavaScript development, and was trying to get ideas for project organization going forward. I've already started putting the frontend/backend in separate subdirectories in monorepos to allow them to be developed independently, and it seems to be working well. However, this repo (https://github.com/karanpratapsingh/fullstack-starterkit) separates the two, but includes a third package.json in the root directory. What's the point of this? I've had experiences where package versions clash due to differences between package.json files in parent and child directories, is there a way to make sure this is avoided if I copy this organization?
-
Code review for an Open Source project
Github: https://github.com/karanpratapsingh/fullstack-starterkit/tree/master/backend-go
-
Fullstack GraphQL starter kit Fall-2021 update
Backend is now available in Go! 🥳
-
What are some fullstack projects that are well-structured and can be studied to learn best practices?
Hi, An opensource graphql first boilerplate https://github.com/karanpratapsingh/fullstack-starterkit might help
-
Fullstack GraphQL starterkit mid-2021 update
Full changelog Github
-
Single TypeScript, ESLint in root, or separate ones for frontend & backend?
I usually set it up at root level, example that might help: https://github.com/karanpratapsingh/fullstack-starterkit
-
Fullstack GraphQL starter kit November update
Full changelog/PR is available here
-
Fullstack GraphQL starter kit October update
Full changelog/PR is available here
-
A note from our sponsor - WorkOS
workos.com | 19 Apr 2024
Stats
karanpratapsingh/fullstack-starterkit is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of fullstack-starterkit is TypeScript.
Popular Comparisons
- fullstack-starterkit VS webiny-js
- fullstack-starterkit VS devhub
- fullstack-starterkit VS Prisma
- fullstack-starterkit VS force
- fullstack-starterkit VS takenote
- fullstack-starterkit VS dogehouse
- fullstack-starterkit VS graphql-code-generator
- fullstack-starterkit VS gqless
- fullstack-starterkit VS Server-Driven-UI