avem Comments - Answer Overflow

Topics

avem

Explore posts from servers

DDeno PD🧩 Plasmo Developers HHono

•Created by Manik Islam Mahi on 12/14/2024 in #help

How can I setup mongoose on deno+next.js app?

@Manik Islam Mahi Do you have types of mongoose schemas shown properly with deno+vs code?

20 replies

•Created by avem on 12/3/2024 in #help

Worried about cold start

Oh, okay, it is time for me to sleep, you meant moving my user data into KV store. Interesting, I will try it in future!

12 replies

•Created by avem on 12/3/2024 in #help

Worried about cold start

Well, replicating data store seems like overkill for my app tbh, maybe on later stages

12 replies

•Created by avem on 12/3/2024 in #help

Worried about cold start

Yeah, totally agree, not saying that Deno to blame here, this is an issue of my app design

12 replies

•Created by avem on 12/3/2024 in #help

Worried about cold start

Most probably I am just a newbie and done something wrong, but meh.

12 replies

•Created by avem on 12/3/2024 in #help

Worried about cold start

Initially I thought that Deno Deploy would be better for my small enterprise, but eventually it becomes a problem of reducing the size of my npm dependies which is just out of scope for my project for now (not a frontend developer). Also apart from having cold start problem it actually worsenes the UX, since my database is in US and having Deno spawning next to the user actually increases time it takes to get data from db, since I am doing multiple of such requests before get the response to the user.

12 replies

•Created by avem on 12/3/2024 in #help

Worried about cold start

moved back to DigitalOcean, but still keeping Deno itself, plan to try Deno Deploy again some time in future https://docs.deno.com/examples/digital_ocean_tutorial/

12 replies

•Created by avem on 12/3/2024 in #help

Worried about cold start

Unfortunately I believe I have to move from Deno Deplay because of the cold starts. No support here, nor in this issue: https://github.com/denoland/deploy_feedback/issues/505

12 replies

•Created by avem on 11/30/2024 in #help

Deno <> Sentry | captureConsoleIntegration and captureException not working?

import { captureConsoleIntegration } from 'https://deno.land/x/[email protected]/index.mjs'

const denoCaptureConsole = captureConsoleIntegration()
denoCaptureConsole.name += '-deno'

import { captureConsoleIntegration } from 'https://deno.land/x/[email protected]/index.mjs'

const denoCaptureConsole = captureConsoleIntegration()
denoCaptureConsole.name += '-deno'

3 replies

•Created by avem on 11/30/2024 in #help

Deno <> Sentry | captureConsoleIntegration and captureException not working?

This helped: https://github.com/getsentry/sentry-javascript/issues/12400#issuecomment-2154636273

3 replies

•Created by avem on 10/14/2024 in #help

Pass context to exception handler

I guess the only way of doing it is to wrap exception and add context? I would like to avoid that since, some of the libraries I use throw exceptions in uncaught promises, which don't allow me to catch them in handler try/catch block.

4 replies

•Created by avem on 10/14/2024 in #help

Pass context to exception handler

// Example route
app.get('/', async (c) => {
    // ....computing the context...
    const context = {
        extensionID: params.extension_id,
        fingerprint: params.fingerprint,
        plan: account.plan(),
        accountID: account.id(),
        extensionVersion: params.extension_version,
        currentPhoto: account.totalUsage() + 1,
        clerkID: clerkID,
        aiMode: params.ai_mode,
        solveMode: params.solve_mode,
        language: params.language,
        joinedAt: account.createdAt(),
    };
    
    // ...some exception happening..
});

// Custom error handler
app.onError((err, c) => {
    // I want to have access to it in here via "c"
});

// Example route
app.get('/', async (c) => {
    // ....computing the context...
    const context = {
        extensionID: params.extension_id,
        fingerprint: params.fingerprint,
        plan: account.plan(),
        accountID: account.id(),
        extensionVersion: params.extension_version,
        currentPhoto: account.totalUsage() + 1,
        clerkID: clerkID,
        aiMode: params.ai_mode,
        solveMode: params.solve_mode,
        language: params.language,
        joinedAt: account.createdAt(),
    };
    
    // ...some exception happening..
});

// Custom error handler
app.onError((err, c) => {
    // I want to have access to it in here via "c"
});

4 replies