Skip to content

fix(vite): remove Deno global check#3401

Merged
marvinhagemeister merged 1 commit into
mainfrom
remove-deno-global-check
Sep 12, 2025
Merged

fix(vite): remove Deno global check#3401
marvinhagemeister merged 1 commit into
mainfrom
remove-deno-global-check

Conversation

@marvinhagemeister
Copy link
Copy Markdown
Contributor

@marvinhagemeister marvinhagemeister commented Sep 12, 2025

Ultimately, it causes more problems than it solves.

Ultimately, it casues more problems than it solves.
@csvn
Copy link
Copy Markdown
Contributor

csvn commented Sep 12, 2025

Ultimately, it casues more problems than it solves.

Maybe a lint rule would be safer? I made #3179 because I feel like it would be easier to add more lint rules in TS rather than Deno core for Fresh. (Though the PR might need some polish)

@marvinhagemeister
Copy link
Copy Markdown
Contributor Author

Yeah a lint rule might be better. Although it's tricky to determine whether a module is used in an island context or not.

@marvinhagemeister marvinhagemeister merged commit 9581d7e into main Sep 12, 2025
10 checks passed
@marvinhagemeister marvinhagemeister deleted the remove-deno-global-check branch September 12, 2025 08:01
@csvn
Copy link
Copy Markdown
Contributor

csvn commented Sep 12, 2025

Yeah a lint rule might be better. Although it's tricky to determine whether a module is used in an island context or not.

Ahh... right. We can't determine any imported components/*, only Islands (/islands/*, routes/**/(islands)/*) directly. 🤔

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

Successfully merging this pull request may close these issues.

2 participants