Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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.

Sign up for GitHub

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

Jump to bottom

Use js extensions for page entrypoints #5

Closed
matthewmueller opened this issue May 2, 2022 · 0 comments
Closed

Use js extensions for page entrypoints #5

matthewmueller opened this issue May 2, 2022 · 0 comments

Comments

@matthewmueller
Copy link
Contributor

matthewmueller commented May 2, 2022 •
edited
Loading

Right now we have entrypoints that have the following format: bud/view/{controller}/\_{action}.{ext}, so for bud/view/index.svelte, the entrypoint would look like bud/view/_index.svelte.

This was nice for understanding the mapping, but doesn't play well with tools that use the extension to determine the content-type, since those served svelte files are actually javascript.

Let's change this, perhaps:

  • .bud/view/index.entry.svelte.js: entrypoint for view/index.svelte (includes hydration + event sourcing)
  • .bud/view/index.svelte.js: compiled view/index.svelte component
@livebud livebud locked and limited conversation to collaborators May 13, 2022
@matthewmueller matthewmueller converted this issue into discussion #20 May 13, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@matthewmueller