Maria José Solano

@mavasani I'm not sure if `public static Location Create(string filePath, TextSpan textSpan, LinePositionSpan lineSpan, LinePositionSpan mappedLineSpan);` is the right overload, since it doesn't fix the different file name issue. Our...

@RobertvanderHulst I'm unaware of your language's design, but you could perhaps achieve this with [LSP](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_codeLens).

I should also mention that if this sounds like a reasonable feature, I would love to work on it!

@tatethurston so changing `href: RouteOrQuery;` to `href: Route["pathname"] | RouteOrQuery;` results in this error message, which I think is clear enough. What do you think?

Hmmm no, in that case we have the error message that you described: However, this seems to be the case with and without my type change.

It seems like the error always shows the same route. Given that this regression isn't caused by my proposed change, are you okay with me continuing with the implementation, or...

Implemented in #84 :)

Although I'm replying to this 5 years later, I'm leaving this here in case anyone else finds it helpful: 1. Watch [this video](https://www.youtube.com/watch?v=tU5ayB6jdK8) from Mads to learn about how to...

For my own learning: @jaywcjlove could you please explain why the following `next.config` is needed? ``` const removeImports = require("next-remove-imports")(); module.exports = removeImports({ experimental: { esmExternals: true } }); ```

@jaywcjlove Thank you for the quick reply! However, it still unclear to me why the `esmExternals` option is needed. From [this Next PR](https://github.com/vercel/next.js/pull/27069) it seems like this package should have...