-
```
1 of 1 error
Next.js (14.2.2) out of date [(learn more)](htt…
-
This probably also applies to other platforms, as the limitation is due to an inaccessible private interface which can actually provide the directory path. You can either include the following private…
-
Right now, the TypeScript compiler targets ES5, which generates non-native JS modules. We don't use Webpack or Babel or anything. The index.html page loads all of the .js files with tags (except thos…
-
### Link to the code that reproduces this issue
https://github.com/joulev/debug/tree/nextjs-some-more-bugs
### To Reproduce
1. `next build`
2. `next start` (or can go here https://debug-git-nextjs…
-
```
Server Error
Error: Module not found: Can't resolve '@deep-f…
-
### What is the problem you're trying to solve
fix staticchcek warnings in volcano reop
```
cmd/controller-manager/app/server.go:84:9: opt.LockObjectNamespace is deprecated: use ResourceNamespace…
hwdef updated
1 month ago
-
The dynamic importing mechanism can introduce unintentional errors when modules are added to the commands dir. Adding modules to the `command` dir causes, `amami` to attempt to import the correspondi…
-
This might be an issue further upstream, but updating to `react-is@16.12.0` breaks dynamic imports.
Works fine using `16.11.0`:
https://codesandbox.io/s/buttermilk-react-is-11-h2pke
But updat…
-
Hello, I guess this could be related to #27.
I am using postcss-critical-css with Webpack 4 (Windows 10) and I am facing the following issue: when importing in the same JS entrypoint several scss p…
-
## Suggestion
For the `import/no-restricted-paths` it would be nice to allow a rule or zone to have exceptions for dynamic imports.
## Reasoning
I am working on using `import/no-restricted-pa…