Solid-start/sockets only in development mode
`createAsync` crashing my app
createAsync
my app crashes:
```tsx
const contactsAndSocial = createAsync(() => getSocialNetworksAndContacts());...Keeping data and code secure and on the server (restrict code to initial render)
"use server";
What already works:
1. OAuth authentication where the client only has a uuid
session but not any of the OAuth keys/tokens
2. When the client fetches a page, server action ... the server resolves the OAuth tokens based on the session UUID...How to update date object?
How does Transition API and createAsync interact?

Retrigger fetcher in createResource on store change
How to catch all errors but keep rendered component?
How to access cookies with ssr?
Unexpected SolidStart Behavior On Vercel. Can You Help?
AuthContextProvider
that works on npm run dev
but doesn't work on Vercel. I'm lost. Any help would be appreciated.
Here's the flow:
1. I'm using a Solid store (createStore
) to store auth state....Hydration mismatch when trying to reference slot element outside of JSX
leadingElement
and trailingElement
that expect a JSX element or fragment. I insert them like this:
```tsx
{local.leadingElement}
// ...
{local.trailingElement}...Context Provider in Layout Component for nested routes in a solid start App is undefined
How Can I Generate A Sitemap?
Inconsistent prop logging between playground and local setup
Receiver
{staticProp: 'Hello', message: 'Hello'}
Receiver
{staticProp: 'Hello', message: 'Hello'}
Possible to define more specific predicated for when prop on Match or Show
How to use preloaded data
How do you recommend using SolidStart to access data for native mobile apps?
POST() { }
and GET() { }
that calls a javascript function like getPostsFromDB
?
API Routes doc: https://docs.solidjs.com/solid-start/building-your-application/api-routes...Environment Variables Missing `npm run start`
npm run build
and npm run start
.
npm run dev
works as expected.
Does the build have access to the .env
file at the root of the project? If not, how do I access them in the build?...Best way to get search params in an API route?
Top level "use server" doesn't seem to work
solid-router: navigate(-1) or navigate(path)? How do we know which?
navigate(-1)
and you'll be back at the home page, one entry previous in the browser history.
But... what if you didn't start at the home page? For example, what if you copy/pasted the user profile URL into a new tab? It would no longer make sense for the back button to call navigate(-1)
because there's nothing to go back to. So in this case it would make more sense for it to call navigate('/')
, adding a new entry in the browser history....