Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A branch for a Deno version #4431

Closed
maddeye opened this issue Feb 19, 2020 · 6 comments
Closed

A branch for a Deno version #4431

maddeye opened this issue Feb 19, 2020 · 6 comments

Comments

@maddeye
Copy link

maddeye commented Feb 19, 2020

Would it be a good idea to open a branch for a Svelte version with Deno instad of Nodejs as the base engine?

Based on a few articles and also on my own tests Deno is more performant and also more secure then Nodejs. Also i could be the way to go for the future.
I don't talk about a replacement, but for simple testing as a first try I think i could be worth the effort.

Can we discuss this here or do you think i would be absolute nonesense?

@antony
Copy link
Member

antony commented Feb 19, 2020

I think if you wanted to create a fork which runs on Deno then you'd be welcome to, and it'd be interesting to see, but the appetite for maintaining a second fork of Svelte officially would be zero, especially given the size of the Deno userbase currently.

@Conduitry
Copy link
Member

The Svelte compiler itself may already almost work in Deno, as it's essentially a pure function that doesn't access filesystem and doesn't require() any Node APIs. It might just be a matter of telling Rollup to output to ESM instead of UMD.

Svelte doesn't work in a vacuum though. It needs a bundler, and I'm not sure how much something like denoland/deno#2467 solves that issue. Then there's the whole suite of bundler plugins that would need some sort of Deno analogue.

In short, if someone else solved all of these problems, and all we had to do was also include an ESM bundle in our package, we'd probably do it. But I doubt we're near that point yet. Closing.

@theArianit
Copy link

I think this needs to be reconsidered now. Deno is getting more popular and more used, and there is a big lack of front-end frameworks for it. Svelte can make use if this situation

@webdeploy-davoli-alessio

I think this needs to be reconsidered now. Deno is getting more popular and more used, and there is a big lack of front-end frameworks for it. Svelte can make use if this situation

I guess it's now considered, looking forward to test this

@maddeye
Copy link
Author

maddeye commented Nov 28, 2022

I think this is an start, but it would be better if you could use Svelte[Kit] directly with deno.
I'm not sure, but this is no easy task and many packages need to be reevaluated and replaced.

@vikaskaliramna0
Copy link

Svelte and SvelteKit works perfectly fine in Deno after they integrated the Node Compatibility layer directly into the core.
But the node_modules still remains an issue when using npm packages like Svelte or SvelteKit in Deno.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants