DummyJSON VS vite

# next auth secret created by open ssl NEXTAUTH_SECRET=8xvug0aweP+j06DbfOLH9fAU7Bf2nLBLnYHQiFPB9Pc= #local NEXTAUTH_URL="http://localhost:3000" NEXT_PUBLIC_API_URL="https://dummyjson.com" # deveploment NEXTAUTH_DEBUG=true

import { useAuth } from "@clerk/nextjs"; import axios, { AxiosError, isAxiosError } from "axios"; interface GraphQLResponse { data: T; errors?: { message: string }[]; } export const useFetchGraphQLData = ( query: string ): ((variables?: TVariables) => Promise) => { const { getToken } = useAuth(); const url = "https://dummyjson.com"; // Replace this with your GraphQL API URL return async (variables?: TVariables) => { const token = await getToken(); try { const response = await axios.post>( url, { query, variables, }, { headers: { "Content-Type": "application/json", Authorization: token ? `Bearer ${token}` : "", }, } ); if (response.data.errors) { throw new Error(response.data.errors[0].message); } return response.data.data; } catch (error) { if (isAxiosError(error)) { const serverError = error as AxiosError>; if (serverError && serverError.response) { const errorMessage = serverError.response.data.errors?.[0]?.message || "Error in GraphQL request"; throw new Error(errorMessage); } } throw error; } }; };

DummyJSON is a set of endpoints you can use to try out different requests without using a commercial API which may or may not ban you or limit your access..

This particular interface was built around https://dummyjson.com/ fake REST API.

https://dummyjson.com has a few good endpoints for building out basic apps.

Buenas te dejo algunas que conozco https://dummyjson.com/ https://www.jsonapi.co/public-api https://github.com/public-apis/public-apis

I've been using https://dummyjson.com/ to prototype my Web Components, but this probably works better.

I will use DummyJSON, to get dummy/fake JSON data to use as placeholder in development and prototyping, without worrying about writing a backend.

import { NextPage } from 'next' import { useState } from 'react' import { setCookie } from 'cookies-next' import { useRouter } from 'next/router' import { useAuthStore } from '~/store/useAuthStore' // import our useAuthStore const SignIn: NextPage = (props) => { // set UserInfo state with inital values const [userInfo] = useState({ email: 'kminchelle', password: '0lelplR' }) const router = useRouter() // import state from AuthStore const setUser = useAuthStore((state) => state.setUser) const setAuthentication = useAuthStore((state) => state.setAuthentication) const login = async () => { // do a post call to the auth endpoint const res = await fetch('https://dummyjson.com/auth/login', { method: 'post', headers: { 'Content-Type': 'application/json' }, body: JSON.stringify({ username: userInfo.email, password: userInfo.password, }), }) // check if response was ok if (!res.ok) { return console.error(res) } // retrieve data from the response const data = await res.json() // check if we have data if (data) { setUser(data) // set data to our user state setAuthentication(true) // set our authentication state to true setCookie('token', data?.token) // set token to the cookie router.push('/') // redirect to home page } } return (

Login

Username (userInfo.email = event.target.value)} required /> Password (userInfo.password = event.target.value)} name="psw" required /> Login

) } export default SignIn

import json import requests def lambda_handler(event, context): base_url = 'https://dummyjson.com/' product_id = '1' resp = requests.get(url=base_url+'products/'+product_id) if resp.status_code != 200: raise Exception('Failed to retrieve product: '+resp.text) return { 'statusCode': resp.status_code, 'body': resp.json() } Q. what this code does? 1.Imports the necessary modules (JSON and requests). 2.Defines a base URL and a product ID that will be used to construct the API URL. 3.Sends a GET request to the API using the requests library, passing in the full API URL. 4.Checks the response status code to make sure that the request was successful (status code 200). 5.If the response status code is not 200, raise an exception with an error message that includes the response text. 6.If the response status code is 200, return a dictionary containing the response status code and the parsed JSON response body. ●Test the function.

As of this writing, initializing a Hattip project requires some manual commands. However, keep in mind that a zero-config development environment based on Vite is in the works.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 4200, } })

For the frontend of "I Disappear," I leverage the automated build & deploy system provided by Netlify, which seamlessly integrates with Vite. This setup ensures that every deployment is optimized for performance, utilizing Vite’s modern build tools to enhance speed and efficiency.

Given our team's collective proficiency within the React ecosystem, we decided to leverage this expertise for our project. Initially, we contemplated utilizing Next.js; however, due to the limited practical experience with this technology among key engineers and the pressing timeline to develop the first prototype, we opted for a Single Page Application(SPA) approach. For bundling, we selected Vite, primarily due to its super fast build times, simplicity of configuration, and potential for a nearly seamless transition to server-side rendering.

We are continuing to add new project templates for various types of projects, and we've recently created one for the infamous combination of React with Vite tooling.

Vite focuses on providing an extremely fast development server and workflow speed in web development. It uses its own ES module imports during development, speeding up the startup time.

Vite and Next.js are both top 5 modern development framework right now. They are both great depending on your use case so we’ll discuss 4 areas: Architecture, main features, developer experience and production readiness. After learning about these we’ll have a better idea of which one is best for your project.

import { defineConfig } from 'vite' import react from '@vitejs/plugin-react-swc' import path from 'path' // https://vitejs.dev/config/ export default defineConfig({ plugins: [react()], server: { port: 3000 }, css: { devSourcemap: true }, resolve: { alias: { '~': path.resolve(__dirname, './src') } } })

I am currently utilizing Vite:

Homepage: https://vitejs.dev/