universal VS react-hook-form

Going to the source code of the CommonEngine we have this:

Angular executes applications in the browser and renders pages in the DOM by default. This default method of rendering in the client comes with disadvantages like poor performance and lack of visibility for search engine crawlers. Luckily, Angular allows us to opt-in for server-side rendering (SSR) through Angular Universal, its official SSR solution.

Example rules based on Angular Universal's gotchas:

About standalone support there's this issue in angular/universal and yes, it is supported now 🥳 Tomorrow I'll try making it work in local

Actually I notice in the last few days they might have done a fix for it = https://github.com/angular/universal/issues/1795

export function app(): express.Express { const server = express(); const distFolder = join(BROWSER_FILES_BASE_PATH, 'angular'); const indexHtml = existsSync(join(distFolder, 'index.original.html')) ? 'index.original.html' : 'index'; // Our Universal express-engine (found @ https://github.com/angular/universal/tree/main/modules/express-engine) server.engine( 'html', ngExpressEngine({ bootstrap: AppServerModule, }) ); server.set('view engine', 'html'); server.set('views', distFolder); server.use( '/browser', express.static(join(BROWSER_FILES_BASE_PATH, 'remix'), { immutable: true, maxAge: '1y', }) ); server.get( '/remix*', createRequestHandler({ build: require('../build/server/remix'), }) ); // Example Express Rest API endpoints // server.get('/api/**', (req, res) => { }); // Serve static files from /browser server.get( '*.*', express.static(distFolder, { maxAge: '1y', }) ); // All regular routes use the Universal engine server.get('*', (req, res) => { res.render(indexHtml, { req, providers: [{ provide: APP_BASE_HREF, useValue: req.baseUrl }], }); }); return server; }

I've located the module that already deals with the GET requests = https://github.com/angular/universal/blob/main/modules/common/src/transfer_http.ts So I've made my own interceptor and replaced the GETs mentioed on lines 75 and 95, however it doesn't seem to work. Only thing I can see is the original code references BrowserTransferStateModule which is crossed out. Do I need to replace that with something else?

Do you inject a token that is provided by SSR? Even though standalone has not reached ExpressEngine, but if you have the root AppModule and the root AppComponent non standalone, you can still use provideHttpClient. To inject a server provided string (specifically, the serverUrl), you can use inject function like this:

React Hook Form is one of the most popular libraries for building forms in React apps with over 39k stars on GitHub. The library has no external dependencies according to Bundle Phobia.

Link: https://react-hook-form.com/

The idea here is to first define an array of field names for each provider. We'll also need a map with more detailed information about each field. This map will contain the field name, label, type, and validation options. We'll use this map to render the form fields and also to validate the form. Finally, we'll have a Form component that will render the form fields based on their type and handle the form submission. We'll use React Hook Form to handle the form state and validation.

Now we need to install React Hook Form because that is the package we are going to use for building our form. We also need to install the package for SendGrid. cd into the sendgrid-contact-form folder and then run this command to install the packages:

Imagine someone unknowingly unleashing heavy computation on a component without useMemo. That computation will run on every component re-render. Not only that, The dependency array in your hooks (useEffect, useMemo, useCallback) are also checked in each re-render. It's like a double whammy for performance pitfalls! I know that you can avoid this by some technique like what react-hook-form done, but remember thats an extra complexity.

But now, all those difficulties are gone since I found React Hook Form and zod.

This will greatly simplify the handling of AJAX forms in React - like for instance for a search form. But again, this may not be enough to get rid of third-party libraries like React Hook Form, which does much more than just handle form submission (validation, side effects, etc).

We could consider to do all these steps specifically for each data-set; of course this isn't an efficient approach due to the amount of repeated code involved. So what if we could abstract all this in a single management? A way to do this could be using a simple configuration in which we specify each aspect for each input (its type, validations required and so on). And we can do this thanks to the extreme flexibility provided by React Hook Form.