D
Deno

help

deno-core adding 40mb overhead

Ttusharmath2/6/2024
We recently migrated to deno-core from mini_v8 and realized a major increase in the size of the release build. Our core runtime is around 12Mb, on which we expected a 20mb increase because of V8, however with deno core we get around an additional 20mb increase in build size, reaching a total of around 50mb. Anyway we can reduce this? Link to our work: https://github.com/tailcallhq/tailcall/pull/1088/files
DAHDeno AI Helper2/6/2024
I wasn't able to find the answer to your question about reducing the build size when using deno-core in the official Deno documentation. However, I can provide some general advice based on the information you've given. When dealing with an increase in build size after migrating to deno-core, it's important to consider what additional features and dependencies deno-core might be including compared to mini_v8. deno-core is designed to be a minimal snapshot of the Deno runtime, but it still includes essential parts of the Deno infrastructure which could contribute to the size increase. Since I don't have access to the specifics of your build process or the exact features you are using from deno-core, I can't provide a tailored solution. However, here are a few general suggestions that might help reduce the build size: 1. Tree Shaking: Ensure that your build process is effectively tree-shaking unused code. This can help eliminate code that isn't actually needed for your application to run. 2. Optimizations: Check if there are any compiler flags or build options that can optimize the build size. Sometimes, different optimization levels can significantly affect the output size. 3. Dependencies: Review the dependencies included in your build. If deno-core is pulling in additional dependencies that you don't need, see if there's a way to exclude them. 4. Assets: If your project includes assets or other static files, make sure they are compressed and optimized for size. Please note that this advice is not based on the Deno documentation, and I would advise you to double-check the accuracy of the advice given. Additionally, since you've provided a link to your work, I would recommend reviewing the changes in the pull request to see if there
DAHDeno AI Helper2/6/2024
are any obvious additions that could be contributing to the size increase. If you continue to have concerns about the build size, you might want to reach out to the Deno community or the maintainers of deno-core for more specific guidance.
Bbartlomieju2/6/2024
You can use deno_core without default features which includes a heavy ICU data file
Ttusharmath2/7/2024
@bartlomieju thanks! We were able to reduce it by 7mb for darwin (53mb to 46mb)

Looking for more? Join the community!

Recommended Posts
Getting errors while using puppeteer in deno environmentHere is my code(supabase edge function index.ts): ```import puppeteer from "https://deno.land/x/pupNon-ascii characters not showing in subject field using Deno SMTPWhen using the smtp library non-ascii characters show up fine in the body. But if included in the heDefault Lint RulesIs there a list of the lint rules that are applied by default. When I look at the documentation it mErrors with mocking & testing in supabase edge function running on deno.Hi everyone - I am sincerely hoping you can save me from pulling out all my hair with this. At my Errors Deploying Fresh ProjectI am new to Deno and working through the Fresh tutorial. I have reached the deployment section: httRun all test in sub-folderHey guys - day one deno newby here. Incredibly inspired by what I've been able to achieve on my firsRead source code contentIs there a way to read the current source code of the a given a file URL (using `import.meta.url`) wDanet create is stuck at databaseWhat am I supposed to do to choose postgres?Working around imports without a file extensionI'm facing an apparent contradiction between the requirements for importing modules, and the import deno runtime extensions seems to be not workingthe example provided here https://github.com/denoland/deno/tree/main/runtime/examples/extension_withcant set up vscode language serveri got some error from the initialization of the language server: ```Starting Deno language server...Choose level for std loggerI have some loggers configured using the `setup` function from `std/log`. This way levels are hard-c