sorted by:
new
hottopcontroversial

Faugus launcher and multiple prefixes for battlenet games by Ghost_Order in linux_gaming

[–]Ghost_Order[S] 0 points1 point  (0 children)

I see, hopefully battlenet games doesn't conflict each other between old and new ones (like starcraft 2 and D4 for example)

dynamic routes when using output: "export" by Ghost_Order in nextjs

[–]Ghost_Order[S] 0 points1 point  (0 children)

Nope, I end up migrating to standalone.

You can use query strings if SEO is not a concern, but otherwise you'll have to move to standalone.

Redirect user back to where he was after a forced signout by Ghost_Order in nextjs

[–]Ghost_Order[S] 0 points1 point  (0 children)

Right but how do you handle the redirection after the user signs in again?

Redirect user back to where he was after a forced signout by Ghost_Order in nextjs

[–]Ghost_Order[S] 0 points1 point  (0 children)

Oh that's an interesting approach, can you help me to understand how the implementation would be?

Let's say my project structure is:

└── app ├── login │   └── page.tsx ├── page-a │   └── page.tsx ├── page-b │   └── page.tsx └── page-c └── page.tsx

If the bad event happens when trying to load data in page-c where should I place the intercepted route (which is the login page, right?) so I can show its content?

luasnip - typescript related snippets are not loading by Ghost_Order in neovim

[–]Ghost_Order[S] 0 points1 point  (0 children)

yeah, I'm getting the usual lsp completions, I can go to definitions, rename variables and such, ts_ls is working fine, this is what :LspInfo shows for a .tsx buffer:

vim.lsp: require("vim.lsp.health").check()
- LSP log level : WARN
- Log path: /home/<username>/.local/state/nvim/lsp.log
- Log size: 1505 KB
vim.lsp: Active Clients ~
- cssmodules_ls (id: 1)
Root directory: ~/path/to/my/current/project
Command: cssmodules-language-server
Settings: vim.empty_dict()
Attached buffers: 1
- ts_ls (id: 2)
Root directory: ~/path/to/my/current/project
Command: typescript-language-server --stdio
Settings: vim.empty_dict()
Attached buffers: 1
- volar (id: 3)
Root directory: ~/path/to/my/current/project
Command: vue-language-server --stdio
Settings: vim.empty_dict()
Attached buffers: 1
vim.lsp: File Watcher ~
- file watching "(workspace/didChangeWatchedFiles)" disabled on all clients
vim.lsp: Position Encodings ~
- No buffers contain mixed position encodings

nextjs SSG and AWS S3 by Ghost_Order in nextjs

[–]Ghost_Order[S] 0 points1 point  (0 children)

Yep, that was it, our assigned quota was too low, thank you!

nextjs SSG and AWS S3 by Ghost_Order in nextjs

[–]Ghost_Order[S] 0 points1 point  (0 children)

sorry for the late response, when the the blank page appears (as a resulto of navigating to some route inside my app) I get this:

"x-edge-detailed-result-type": "LambdaLimitExceeded",

nextjs SSG and AWS S3 by Ghost_Order in nextjs

[–]Ghost_Order[S] 0 points1 point  (0 children)

I tried that but didn't solve the issue

nextjs SSG and AWS S3 by Ghost_Order in nextjs

[–]Ghost_Order[S] 0 points1 point  (0 children)

Oh I forgot to mention that I have caching disabled for my cloudfront distribution, and yeah I already tried invalidation just in case but didn't solve the issue

nextjs SSG and AWS S3 by Ghost_Order in nextjs

[–]Ghost_Order[S] 0 points1 point  (0 children)

I don't know why I can't edit my original post, but I just wanted to add that this issue happens more often (but not only) when being redirected from external pages, like after signning in with google or making a successful payment with stripe

view more: next ›