You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I'm building a toy project with caldera to make sure it could be useful in a future project.
First of all, I have to say that all JS / TS related features work great out of the box and the api design is very simple, which is good for something so powerful.
But, my problem arise when you try to serve css from the same server.
Here is an example repository that can be used to reproduce the whole affair.
As you can see I'm using tailwind, but that should be unimportant in that matter as they generate a static css file at compile time.
The problem is located on the page load, Head does its job of writing to the head tag, but the call to retrieve that css is always answered with an index.html that, I assume, caldera did generate.
What I think is happening is that you catch all incoming request and always serve the caldera root, but that cannot work to support other ressources.
Maybe I'm missing something, I would be glad to know that caldera just work, but for the moment it seams to only support external css, as the examples shows.
The text was updated successfully, but these errors were encountered:
Hello, I'm building a toy project with caldera to make sure it could be useful in a future project.
First of all, I have to say that all JS / TS related features work great out of the box and the api design is very simple, which is good for something so powerful.
But, my problem arise when you try to serve css from the same server.
https://github.com/Methrat0n/caldera-toy-project
Here is an example repository that can be used to reproduce the whole affair.
As you can see I'm using tailwind, but that should be unimportant in that matter as they generate a static css file at compile time.
The problem is located on the page load,
Head
does its job of writing to thehead
tag, but the call to retrieve that css is always answered with an index.html that, I assume, caldera did generate.What I think is happening is that you catch all incoming request and always serve the caldera root, but that cannot work to support other ressources.
Maybe I'm missing something, I would be glad to know that caldera just work, but for the moment it seams to only support external css, as the examples shows.
The text was updated successfully, but these errors were encountered: