Get Fresh working in Node
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- node.js, typescript, vite
- Domain
- backend, build-system
Research direction
Start with the import chain in packages/plugin-vite/src/mod.ts, packages/plugin-vite/src/plugins/server_entry.ts, packages/fresh/src/internals_dev.ts, and packages/fresh/src/dev/builder.ts, then inspect the referenced middleware.tsx and the installed @fresh/core package. Check why the .tsx source has no corresponding compiled .js file and whether the cause is Fresh packaging or JSR. Done means the Vite config loads in Node with @fresh/plugin-vite.
Written by the indexing model from the issue text.
Description
I'm trying to see if @fresh/plugin-vite can be made to work in Node (not Deno). One of the issues I've run into is that this package depends (indirectly) on a .tsx file, which results in the vite config failing to load.
I've traced it to the middleware.tsx file.
Import chain
For some reason, the @fresh/core JSR package, when installed through npm/pnpm, does not contain the compiled .js files next to the .tsx source files. This is unlike the .ts files, each of which does have a corresponding .js file next to them. There is no easy way to "inspect" this on the web, but you can verify it by running pnpm install jsr:@fresh/core and looking inside the node_modules folder (see screenshot).
This could either be some misconfiguration or a potential bug in JSR. I saw https://github.com/jsr-io/jsr/issues/24#issuecomment-2677117503 which claims that JSX is supported, so this scenario is supposed to work in theory at least.
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 757
- Avg merge
- 3m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from freshframework/fresh
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
freshframework/fresh#3833 ·
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
freshframework/fresh#3803 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
freshframework/fresh#3918 · 1 comment · 4 reactions ·
-
Tab title doesn't update to <Head> <title> when navigating to a page with another <title>Possibly taken @1AbdullahButt claimed this 7 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 57/100
freshframework/fresh#3916 ·
All issues in freshframework/fresh
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day