SOLVED: createLazyMemo Broken?
How to use useSubmission with server action passed to form?
Struggling with load function and cache revaliation
Basic store example is not reactive
setStore TypeScript Issue
Redirect troubles
Error: Cannot find cache context
Phosphor icons
web
package and import the .css
file. I see that exists a package for Solid, but in terms of performance, this usage with the web
version is a problem?...`bun create solid` takes long time to create a new project
bun
to create new project. After running bun create solid
and choose with tailwindcss
template, the process stuck at the step of Creating Project
without any file created in my project folder. Has anyone every come across this issue before?Is there a convenient way to check the permissions of a user
How to route `products/[id]/settings` in Solidstart?
example.com/products/1/settings
```
|--routes/ // example.com
|--products/...(Vinxi)Error while deploying a project generated by Solid Start
pnpm create solid
and then chose the basic template just for testing
anyways this is my package.json ```{
"name": "example-basic",
"type": "module",
"scripts": {...this is undefined
Is the `solid-element` library still being maintained?
SuperTokens
to create a set of reusable Web Components, and the team was interested in using solid-element
to get the job done. However, there doesn't seem to be extensive documentation for this tool, and it hasn't gotten an update for quite some time.
Is the recommendation to use something else like lit-html
for creating Web Components? And is it safe to assume that solid-element
is "Use at your own risk", or will it be getting more attention later?...Issue with localStorage and signals
Proper Usage of load() for Authentication and Redirection in Solid-Start
Different header for specific routes
Returning Errors and not throwing
Rather than throwing errors, it is recommended to return them from actions. This helps with the typing of submissions that would be used with useSubmission. This is important when handling progressive enhancement where no JavaScript is present in the client, so that errors can be used declaratively to render the updated page on the server.
Rather than throwing errors, it is recommended to return them from actions. This helps with the typing of submissions that would be used with useSubmission. This is important when handling progressive enhancement where no JavaScript is present in the client, so that errors can be used declaratively to render the updated page on the server.
With Solid Auth template, I get "UnknownAction: cannot parse action at /api/auth/session"
Is this a good method to secure routes?