Add support for deno

[Evian-Zhang]

Feature request

Is your feature request related to a problem? Please describe.

As deno is going to have its 1.0 release at May 13, will next.js add support for deno?

[tsujp]

Any progress on this?

EDIT: I realise my folly, #12334 (comment)

[timneutkens]

@tsujp feel free to contribute to making it work.

[tsujp]

Planned to have a gander, wanted to chime in here just in-case there are parallel efforts going on.

[lemarier]

Hi @timneutkens, I would love to help on this. Something have been planned?

Did you guys have an idea of what need to be done exactly?

Thanks

[timneutkens]

In this case it’ll be entirely up to the people that want to land it. I assume you’ll have to figure out how to run webpack/Babel in deno first though.

[tsujp]

I was a bit naive in my "progress on this" above. All the dependencies of Next, and their dependencies' dependencies etc will need to work with deno before Next could -- so I suppose "progress on this" is more of a "progress on deno for production?". I have also heard various people are trying to get dependency auditing (e.g., deno_udd) fleshed out. So these kinds of tools have to be more mature also.

Whoops.

[kachkaev]

There is a new project called Aleph.js, which is

The React Framework in Deno, inspired by Next.js.

GitHub: https://github.com/alephjs/aleph.js

Could be worth watching the space to cross-pollinate some ideas 🙂

[baer]

At the time of writing, the babel team does not have any plans to support Deno.

babel/babel#11543 (comment)

[jerrygreen]

I love how this issue has good first issue tag, while it’s nearly impossible for NextJS to support Deno. Maybe they can just morally support and say: “Hey guys, gl in whatever you’re doing!” and be done with it, but everyone will consider this 126% rude, so silence is better 😂

Honestly the last time I checked Deno when v1 came out, it was quite poorly working for Windows, and all the feedback I got from their somewhat-core team was almost like: “windows? hah we’re having some kid here not knowing that you have to use Linux to develop things... use WSL” (well, he said somewhat like this), but WSL is almost like little virtual Linux machine, so mehhh... While NodeJS is working without any virtual machine layer completely fine, it’s a shame Deno can’t be run that easily too. So despite Deno v1 came out, they still have a lot of work to do to improve their fundamental things like cross-platform support (at the very least)

Their core-core member Ryan Dahl sympathizes me actually: he has good vision, good ideas, so maybe some Deno v2 will be much better and more production-ready, who knows... 💕waves tons of support 💕

[shadowtime2000]

@jerrygreen It seems your points about Deno needing to improve cross-platform support is based on Deno v1 which was released around a year ago. I have been using Deno and plain old Windows without WSL for AlephJS and other projects, and it has been working great. You can't really base it's flaws around the v1 release which was around a year ago. I recommend you download the latest Deno, v1.8.2, and try it out because those "fundamental things" have been worked on.

[jerrygreen]

@shadowtime2000 time flows fast 😅 Thank you for saying all that, I’ll keep in mind Deno deserves another try.

I saw AlephJS back in the days too, and yeah: if you wanna use Deno and want NextJS then AlephJS is definitely your choice, despite having some differences it fits the most.

For some other things, like Electron, people do have equivalent questions though:

electron/electron#23613

Unfortunately there’s no such thing as Denotron or something 😞 Nor there’s support from Electron (neither currently nor in plans). If there would be, I would be probably making my projects with Deno already