Vercel
Vercel is the optimal workflow for frontend teams.
All-in-one: Static and Jamstack deployment, Serverless Functions, and Global CDN.
Here are 4,016 public repositories matching this topic...
Bug report
Description / Observed Behavior
Passing an updated fetcher method to useSWR has no effect. The initial version of the fetcher will be used.
I am passing a fetcher function to useSWR that is updated by applying a new access token.
const [accessToken, setAccessToken] = useState("valid-0");
const fetcher = () => {
console.log("fetch with token:", accessToken-
Updated
Nov 4, 2021 - JavaScript
-
Updated
Dec 17, 2021 - JavaScript
-
Updated
Nov 16, 2021 - TypeScript
-
Updated
Dec 20, 2021 - TypeScript
-
Updated
Dec 20, 2021 - TypeScript
-
Updated
Dec 20, 2021 - HTML
-
Updated
Nov 24, 2021 - TypeScript
-
Updated
Dec 14, 2021 - Python
Feature request
The account details page is set up to imply that you can update your account. Entry forms and buttons that actually update these things in the database would be nice.
Describe the solution you'd like
An example of updating the name (so I can implement the email update), or full implementation by default.
Describe alternatives you've considered
Currently goin
-
Updated
Dec 21, 2021 - JavaScript
-
Updated
Dec 20, 2021 - JavaScript
-
Updated
Dec 17, 2021 - JavaScript
-
Updated
Dec 17, 2021 - TypeScript
-
Updated
Nov 19, 2021 - JavaScript
-
Updated
Nov 15, 2021 - JavaScript
-
Updated
Dec 21, 2021 - TypeScript
-
Updated
Sep 1, 2021 - JavaScript
[BUG] Broken links
Description of the bug
Description
Code implementation links of algorithms when opened are giving 404 errors. I observed such behavior for Bubble sort.
Actual behavior
- Go to https://the-algorithms.com/algorithm/bubble-sort
- Scroll down to Code Implementation links
- Click on Java
Actual behavior
4. See Github 404 page (the link is https://github.com/TheAlgorithms/Java/blob/ma
- Organization
- vercel
- Website
- vercel.com
Describe the feature you'd like to request
As per the docs: https://nextjs.org/docs/advanced-features/custom-document#caveats
styled-jsx is not allowed inside custom
_document.jsand I was getting 500 errors on all SSR pages when deploying a site to production that had a<style>tag inside a custom_document.js.I think it's a good idea to add an ESLint rule to remind users about