일 | 월 | 화 | 수 | 목 | 금 | 토 |
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | 6 | 7 |
8 | 9 | 10 | 11 | 12 | 13 | 14 |
15 | 16 | 17 | 18 | 19 | 20 | 21 |
22 | 23 | 24 | 25 | 26 | 27 | 28 |
29 | 30 |
- CLASS
- graphQL
- Interface
- tailwindcss
- solidity
- node.js
- blockchain
- nextJS
- useState
- Ethereum
- Props
- REACT
- JavaScript
- middleware
- Redux
- typeScript
- CSS
- 삶
- express.js
- API
- evm
- concept
- web
- error
- built in object
- hardhat
- 기준
- HTML
- SSR
- bitcoin
- Today
- Total
목록nextJS (33)
ReasonJun
What happened? In the case of ts-node, ts was compiled using the commonJS method. Therefore, an error occurs when you try to run a ts file with ts-node in the app or src subfolder of nextjs, which is compiled with esNext. Error : https://github.com/TypeStrong/ts-node/issues/935 `ts-node` fails when ES Modules are in the dependency graph in Node.js 13+ · Issue #935 · TypeStrong/ts-node I basicall..
Next.js has a default caching mechanism aimed at enhancing performance and cost-efficiency. By default, it employs static rendering for routes and caches data requests unless you specifically choose not to use caching. Here's a summary of the default caching behavior: Static Route Rendering: Routes are statically rendered at build time. This means that during the build process, Next.js generates..
Server Actions: React’s first steps into mutability Within the context of RSCs, Server Actions are functions that you define in an RSC on the server side that you can then pass across the server/client boundary. When a user interacts with your app on the client side, they can directly call Server Actions which will be executed securely on the server side. This approach provides a seamless Remote..
error: Why: Basically this working message comes. Because of eslint. "next/babel" is basically the presets that are created by Next for the eslint. Solution: Reference: https://www.youtube.com/watch?v=nEA1wS3ZncU https://nextjs.org/docs/pages/building-your-application/configuring/babel Configuring: Babel | Next.js Using Pages Router Features available in /pages nextjs.org
code: Error not scrolling after navigating to '/User/Transactions/' const onDelete = () => { setLoading(true) axios .post('/api/delete/my-transaction', { transactionId: transactionId }) .then(() => { toast.success('Complete deletion of transaction'); router.push('/User/Transactions/'); }) .catch((err) => { toast.error(`Fail: The delete failed.`); console.error(err); }).finally(() => { setLoading..
While developing the web3 web app, the following error occurred during the metaMask linkage process. Currently, the metamask side has received the problem and the resolution is in progress. This error is solved once the metamask is disabled. Removing intrinsics.JSON.rawJSON Removing intrinsics.JSON.isRawJSON Removing intrinsics.%ArrayPrototype%.toReversed ... https://community.metamask.io/t/erro..