Bug report

Describe the bug

Next encounters an unhandled error when handling /api in local and production using Next 9 Routing. We are not using the API Routes feature.

To Reproduce

Create a Next app with a /[foo] page using Next 9 Routing.

1. Go to '/api'
2. Get a full unhandled 500 ISE.

Expected behavior

/api is routed to /[foo].

Screenshots

<img

Looks closely related to #779

I'm submitting a...

[ ] Regression
[x] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Middleware is being called for every endpoint a request route could potentially match.

Is there an overview, how the config object for the constructors of the neural network are defined?

This would be interesting:

• Has brain.NeuralNetwork and brain.recurrent.RNN the same config attributes?
• What is the description of the inputSize attribute?

Thank you for the great work with this library, it is realy amazing!

There are two mentions of a reactide.config.js file in the README:

The component tree works out-of-the-box by finding the entry point to your React application that you provide inside the reactide.config.js file.

Go to the reactide.config.js file and change the .html and .js entry points to the relative path of your respective files.

But I could not find any examples or documentation

This page of the docs for rest data sources isn't working anymore:

https://www.apollographql.com/docs/apollo-server/serving/data-sources/#rest-data-source

I see that the page still exists in the docs which makes me think this is an error:

https://github.com/apollographql/apollo-server/blob/master/docs/source/data/data-sources.md

Was it moved somewhere else?

Hi, if you are reading this is because you pretty likely don't know how to start 🤔 . Fair enough !

So, let's fix that 🚸 !

What should I know before start?

All here we are developers with different backgrounds, languages and objectives. But, all we must follow certain rules so we can understand each other and make the communication easier as possible. Please 👍 read your [code of conduc

AWS Lambda currently supports Node v10.x
Can you please support it.

When using git cz, one option for a type to select is "improvement", but this fails the enum check

husky > commit-msg hook failed (add --no-verify to bypass)
git exited with error code 1
kris@Kriss-MacBook-Pro cent-admin % git cz
cz-cli@4.0.3, cz-conventional-changelog@3.0.1

? Select the type of change that you're committing: 
  revert:      Reverts a previous commit 
  feat:

pnpm version:

3.8.1

Code to reproduce the issue:

I have a repo containing multiple packages. I have a package.json file at the root to define some scripts. Since I do not have any dependencies in this package.json, there is no lockfile created.

I want to run pnpm recursive outdated to see if there was any outdated dependencies in my packages. Unfortunately, I got the follow