nextjs
Here are 5,275 public repositories matching this topic...
-
Updated
Sep 3, 2019 - TypeScript
If the file doesn't exist then no sha is found. In this case it should throw an error.
What do you want and why?
Currently we export everything from our internal files, including things that are not supposed to be part of our public API.
We need to change that and explicitly export only what is for public consumption.
If you work on this, feel free to ask me as many questions in slack a
-
Updated
Oct 5, 2020
-
Updated
Sep 27, 2020 - TypeScript
-
Updated
Aug 17, 2020 - TypeScript
-
Updated
Sep 7, 2020 - JavaScript
-
Updated
Jul 18, 2019
-
Updated
Sep 25, 2020 - JavaScript
Some folks have noted it would be beneficial to have this repository translated to other languages. One contributor has already volunteered to translate the repository into Russian (woohoo!).
If anyone has the time and drive to help out with other languages, please reply below with the proposed language and I'll give you the "go-ahead"... just to make sure two people don't create translations i
-
Updated
Sep 30, 2020 - TypeScript
-
Updated
Sep 8, 2020 - TypeScript
-
Updated
Oct 4, 2020 - TypeScript
-
Updated
Sep 25, 2020 - TypeScript
-
Updated
Sep 6, 2020 - JavaScript
Describe the bug
When running npx serverless --debug
if the next build
process fails with an error it is not displayed in the output and the deployment hangs forever.
To Reproduce
Steps to reproduce the behavior:
- Create a reproducible error in
pages/index.js
(in my case animport
statement was incorrect) - Run
npx serverless --debug
- Output displays "appName Deplo
-
Updated
Jul 17, 2020 - JavaScript
-
Updated
Oct 5, 2020 - JavaScript
-
Updated
Oct 5, 2020 - JavaScript
There is an import dependencie cycle between:
src/Interfaces/index.ts
:
export * from '@Redux/IStore';
and
src/Redux/IStore.d.ts
:
import { IHomePage } from '@Interfaces';
Eslint rule that detect the issue:
https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-cycle.md
Improve this page
Add a description, image, and links to the nextjs topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the nextjs topic, visit your repo's landing page and select "manage topics."
Feature request
As a user of [x] framework/language, I'd love to see an easy path towards migrating to Next.js
Describe the solution you'd like
Documentation around common providers and how exactly you can switch to Next.js from them.
Additional context
Let's start with a few of the most popular and see what others in the community would get value from.