restfuncs
react-specials
restfuncs | react-specials | |
---|---|---|
10 | 5 | |
31 | 5 | |
- | - | |
9.7 | 5.5 | |
12 days ago | 4 months ago | |
TypeScript | JavaScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
restfuncs
-
[AskJS] What do you use to make small back-ends ?
Putting restfuncs into the round (as the communication lib).
-
Restfuncs 2.0 release (an RPC + REST server + Client) - how do you like the new API ?
Hi, finally, after a complete redesign of the API, i'm releasing the new 2.0 Version of Restfuncs. Much effort went into the CSRF protection, which i'm kind of proud now, to be one lib that does take much care about this. Still it's a little work-in-progress, as you see, but if you like, you can already start using it and wait, til it's production ready (+ help the typescript-rtti guys to get that lib stable ;) ). The Restfuncs API should be stable and stay on 2.x major version for a while.
-
I've made playground demo of typia - 20,000x faster validator
OK, that's cool. Looking for something for the restfuncs lib. Currently i'm using typescript-rtti but i'm open to such stuff if the security is good. And fast validation sounds very very good ;)
-
How to make a NodeJS REST API most efficiently?
Here's one library that i'm making for that. Currently it's focused to make functions callable via RPC. But i'm working on a comprehensive REST interface currently. It's already in the docs on the github repo. Hope that is kind of what you are looking for.
-
Serving react statically with express
See this example and use the dev_faster... run script. It uses a dev/production switch to see if it should run the devserver or host the pre-build static files as you see when you look at server.ts
-
Is my concept right or convince me, why CSRF tokens are really needed.
Yes, behaviour will also be documented in the library's doc under security (not yet done, cause i'm the middle of writing) The library is all about that, so no maintainer will quickly change those core security lines without having understood them. Additionally i've written cross site security testcases which test every line of these ;)
-
TypeScript rant
Here's a simple sample project which host the vite devserver inside express for development (so you don't have a chaos with different processes / ports / origins). This should be the way to go.
-
Nodejs setup with typescript
Or, for a quick client-server app, use this
-
What’s the hype with Vite?
See this example starter application stack, with client/server communication, cramped down to a ridiculously few lines of code / files - you can't underbeat that.
react-specials
-
Thinking about making a MERN Stack project while learning about it, but don't know what's the best place to start learning/building
I built a MERN stack project as my first full stack project. Here's the repo: https://github.com/cagross/react-specials
-
Serving react statically with express
Yes, this is indeed how my project is organized (repo here).
-
MERN stack deployment
I have a MERN app, and the React app and Express app are both deployed together (using cyclic.io). You can see the repo here, if you want to see how I set up my folder structure. Basically, the root of the folder is a Node project--the Express app. In a sub-folder i've installed a second Node project--the React app. Then the main Express file needs some lines to tell it to properly server the React app to certain routes.
-
Pushing to Heroku from local is being rejected. Is it because my Node project no longer has a package.json file in its root directory?
Is that right? I've been committing my React build directory to Git since I begain the project. You can see the repo here. What are the disadvantages of committing the build directory? I get that it can unnecessarily bloat the size of the repo in many cases, especially in cases where Heroku builds the same files anyway. But in my case, the size of the build directory is only ~300 kB. So maybe that's an acceptable tradeoff, in order to implement an easier solution to my issue? Or do you still think I should go the two-Heroku-app solution?
What are some alternatives?
vite-plugin-checker - 💬 Vite plugin that provide checks of TypeScript, ESLint, vue-tsc, Stylelint and more.
webpack-dev-middleware - A development middleware for webpack
nodejs-setup - Quick node.js 2023 boilerplate setup
concurrently - Run commands concurrently. Like `npm run watch-js & npm run watch-less` but better.
karma-typescript - Simplifying running unit tests with coverage for Typescript projects.
vitest - Next generation testing framework powered by Vite.
NodeFuel - NodeFuel is a TypeScript-first boilerplate for building high-quality Node.js apps with multi-authentication using Passport. Get started today and fuel up your Node.js development!
typia - Super-fast/easy runtime validations and serializations through transformation
vite-vs-next-turbo-hmr - Benchmarking Vite vs. Next + turbopack HMR performance