Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error when compiling

See original GitHub issue

I started receiving this error on a Nextra project: I tried deleting almost any file and the error is still there (either with Node 12.x or 14.x). I tried also removing the .next folder, the node_modules folder and the yarn.lock file and reinstalling modules, but I still get the error.

The repo is here: https://github.com/ReactBricks/react-bricks-docs

Thank you, Cecilia

(node:11513) UnhandledPromiseRejectionWarning: TypeError: Cannot read property '1' of null
    at removeExtension (/Users/cecilia/Documents/Development/react-bricks-docs-v2-nextra/node_modules/nextra/dist/loader.js:70:32)
    at /Users/cecilia/Documents/Development/react-bricks-docs-v2-nextra/node_modules/nextra/dist/loader.js:90:42
    at Array.map (<anonymous>)
    at getFiles (/Users/cecilia/Documents/Development/react-bricks-docs-v2-nextra/node_modules/nextra/dist/loader.js:88:44)
    at async getPageMap (/Users/cecilia/Documents/Development/react-bricks-docs-v2-nextra/node_modules/nextra/dist/loader.js:143:11)
    at async Object.loader (/Users/cecilia/Documents/Development/react-bricks-docs-v2-nextra/node_modules/nextra/dist/loader.js:177:26)
(node:11513) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:11513) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

2reactions

shudingcommented, Dec 17, 2020

Fixed in #62, thanks to @fanweixiao. Also released nextra@0.3.2.

2reactions

gsimonecommented, Dec 17, 2020

This happened to me when OSX created a .DS_Store in the pages dir, solved by removing it

Top Results From Across the Web

7.3. Compile Errors and Warnings

A compile error happens when the compiler reports something wrong with your program, and does not produce a machine-language translation.

Understanding and fixing compiler and linker errors

Errors are conditions that prevent the compiler from completing the compilation of your files. Compiler errors are restricted to single source code files...

Difference between Compile Time Errors and Runtime Errors

Compile-Time Errors: Errors that occur when you violate the rules of writing syntax are known as Compile-Time errors. This compiler error ...

What Is a Compilation Error? (with picture) - EasyTechJunkie

A compilation error is an error in building a machine code file for a computer language. Many computer languages compile their source code ......

Fix the top 10 most common compile time errors in Java

As the name implies, compile time errors occur when the code is built, but the program fails to compile. In contrast, Java runtime...