Viktor Vincze
Viktor Vincze
I was also about to open a feature request for a similar case. In my codebase, I heavily rely on `path-to-regexp` features. The upgrade docs say to move such logic...
They justified the removal in the changelog/upgrade docs. The main reason is size, `path-to-regexp` is big. I also believe it has to do a bit with `Remix` as they are...
Nice, the matcher prop does exactly what we wish for here and it has a react-router compatible API. Thanks for sharing. On Mon, Dec 13, 2021, 16:44 bluepeter ***@***.***> wrote:...
You successfully handled 1 specific case from many with an ugly hack. This just validates stronger the concerns many of us have. On Fri, May 20, 2022, 19:20 bluepeter ***@***.***>...
For me that's not working. Let's say I have a title `Lorem ipsum`, searhing for `orem` doesn't giving any result.
Maybe this can help you: https://ccss.dev/
I also noticed the same, it's Chrome 99 on my phone, so SharedArrayBuffer shouldn't be a problem. I inspected the page and this is the log/error: ``` [info] use ffmpeg.wasm...
- For the first case when I'm doing `require.resolve('@/aliasedpath/moduleDirWithIndexTsFile')`, it won't get resolved. I could use https://nodejs.org/api/modules.html#modules_require_extensions but it's deprecated so I thought it would be nice to have such...
I'm using TS in runtime with babel-register so I don't have dist folder, only src.
+1 for @danielhaim1's problem, we're facing with the same issue. I was actually amazed when I saw this is not an existing feature.