Egg: [Feature Request] Have you considered making a new version by deno

Created on 22 May 2020  ·  1Comment  ·  Source: eggjs/egg

Background

As u know ,problems cause by node_modules

Proposal

for build faster,run safer, migration easier.

Additional context

Inactive

Most helpful comment

No obvious gains.

deno is too young, needs more time to prove itself.

  • faster: most of the time, and most of the usage, maybe change readFileSync to readFile or just wait and upgrade node v8 will make you faster and faster.
  • safer is important for CLI, but for server safe && mini docker is more important.
  • node_modules is not good enough, but I don't see DO NTH at deno is a better solution( how could you update you deps, by modifying each version in every file???) and should we had to build all the wheels we made these year to deno version?

>All comments

No obvious gains.

deno is too young, needs more time to prove itself.

  • faster: most of the time, and most of the usage, maybe change readFileSync to readFile or just wait and upgrade node v8 will make you faster and faster.
  • safer is important for CLI, but for server safe && mini docker is more important.
  • node_modules is not good enough, but I don't see DO NTH at deno is a better solution( how could you update you deps, by modifying each version in every file???) and should we had to build all the wheels we made these year to deno version?
Was this page helpful?
0 / 5 - 0 ratings