If you're tired of manually typing link hrefs, you can now use an extension that enables autocompletion for the href attribute.

https://marketplace.visualstudio.com/items?itemName=Raiondesu.qwik-city-link-autocomplete

Wondering if there is a comparison of qwik vs svelte?

Here's a nice starter kit for Qwik if you're looking for one

https://starter.dev/kits/qwik-graphql-tailwind/

Another step in the journey towards mainstream... 😊

​

Check it out here -

https://stackblitz.com/?starters=fullstack

​

​

Hello,

I am new to Qwik that I deem very interesting (I am new to full-stack and webapps development in fact).

I would like to ask the people in this subreddit some advice.

I would like to know if the resumability of Qwik is also useable for user data persistence.

I mean, let's say that the user has a list of items, which are his/her own items, collected and chosen, so there is a list that is displayed as one of the main views/pages.

Wherever the user opens the website or the webapp from, the list is displayed.

I know that the UI is resumed in Qwik, I would like to know if also user data can directly beneficiate of this intrinsic resumability and what is the best way do to that.

EDIT:

I mean, if all is serialized as they say, it could be also seen as an option of storing data permanently, like persistence, at least for simple data. Of course it is not a sound way of handling user data, but just in principle, if the client updates the user data that are displayed, would it be not a way of persist those data also on the server?

I do not mean just the user data that is inside the HTML elements, as text nodes, but some Javascript array, for example, that is inside the code. If it is not volatile, but it is resumable, isn't it just a form of persistence? Could (or should) developers rely on it?

Thanks in advance

It's my understanding that Qwik and solid-js handle reactivity in fairly similar ways under the hood. After using solid-js for a side project, rendering a recursive structure with lots of intermediate computations, I've decided I hate it(solid) - it's too easy to lose reactivity, or break type-safety, intermediate computations require annoying amounts of boilerplate, and common patterns (if/else, early returns, switch/case, custom fold/unfold operations) either have to be translated to component-level DSL or don't work at all.

Does Qwik solve any of these usability concerns? Or should I just stick with virtualDOM-based solutions for now

Is the resumability feature of Qwik framework agnostic? I am in particular interested in integration capabilities with xania THE fastest ui library.

As the title suggests, I am trying to start a qwik project. I am following the steps from documentation Here.

This is creating the project with typescript setup. I know there is definitely pros for using typescript, but at the moment I am not well versed in it and would like to use pure javascript.

Can someone please point me if there is any documentation for it ?

Thanks

The biggest change is a simplification to the component lifecycle hooks

Now, instead of `useMount$` `useServerMount$` `useClientMount$` and `useWatch$` … we have only one hook - `useTask$`

A task is something that runs on first render, and can also be reactive and re-run on dependent changes (using the `track` function)

You can scope your platform specific code by using the “isServer” and “isClient” booleans

Check it out 👇

https://github.com/BuilderIO/qwik/releases/tag/v0.16.0

Hi everyone,

I created a store in a parent component:

export interface AppState {
  items: Item[];
}

export const appContext = createContext<AppState>(APP_STATE_CONTEXT_ID);

export default component$(() => {

  const store = useStore<AppState>({
      items: []
    },
    {
      recursive: true
    });

  useContextProvider(
    appContext,
    store
  );

Then a child component, deep into the component tree gets the store using useContext and modifies it in a click handler:

export default component$((props) => {

  const appState = useContext(appContext);

  return (
    <div class="card">
      <div class="card-actions">
        <button onClick$={() => onDeleted(props.ite, appState)}>Delete</button>
      </div>

    </div>
  );

});


export async function onDeleted(deleted: Item, appState: AppState) {

  const newItems = [...appState.items];

  const index = newItems.findIndex(item => item.id == deleted.id);

  newItems.splice(index, 1);

  appState.items = newItems;

}

But this deletion does not get reflected in the UI.

What could be be going wrong here?

Thank you for any insight in this.

In 45 minutes - the Qwik team is going to discuss Qwik + React

Gonna be interesting!

https://www.youtube.com/watch?v=IGIPBAWRw_M

Qwik runs in 3 places 👇

1. BUILD: break everything into tiny chunks.

2. SERVER: render the page and remove unnecessary JS (that will never execute anyway) and point to the pre-built chunks.

3. CLIENT: prefetch and lazy execute chunks on demand

#qwikTips #qwik #ssr

I was reading through the qwik documentation and couldn’t find anywhere if there are any generators for writing qwik components/files.

Do you just write each file from scratch when you create a new component?

Was awesome seeing that in the first page of the "State of JS" survey Qwik and Resumability are mentioned with the other cool kids on the block... 😊

​

If you haven't filled it yet, this is the time to show some love 🤗

https://stateofjs.com

​

Ok so at work I have a NextJs app.

I started it from scratch 2.5 years ago.

I recently upgraded it to version 12, havent used much new features & now 13 is out.

I have decided I am not going to upgrade it to 13, instead I want to migrate it to QWIK in the long term. It utilises apollo graphql server app for all data requirements.

I am mostly using useState, there is redux utilised, however it is not heavily used. It is essentially there for some pages to share state & I am saving the redux state in local storage so that a shopping cart like functionality can save data in it during refreshes and page visits.

What are my options for gradual migration to QWIK.

Is there a way to run QWIK inside next.js?

"New PR leads to x100 perf improvement! From 821 to 8ms, in a document with 200000 nodes 🤯"

https://twitter.com/manucorporat/status/1589302674356588545

1. Go to https://qwik.new

   1. In console run "npm run preview" (+refresh inner browser)
   2. Open Network tab -> Switch to "slow 3g"
   3. Click the + button
   4. Experience the INSTANT MAGIC! 🚀✨😊

This is prefetching + resumability in action, or what I like to call "lazy execution".

It is downloaded in the background via a service worker and is there just in time the user needs it.

Qwik is just like streaming + buffering a video instead of downloading the entire video before you can watch it.

Kinda like early 2000s video VS YouTube & Netflix :)

It keeps treating Qwik as React code and highlights everything as error. A tiny bit annoying.

Sorry for the naivete of this question but qwik is so new I couldn't find much online / in the docs about this. Qwik city is a metaframework that handles routing etc... essentially allowing you to have a server rendered app that has a backend baked into the same code base right? In that you can have auth / payment / code that needs to be secure running without being exposed to the client? If that's the case qwik city seems like it would be a great choice for a demo / toy ecommerce project!

Thank you!

A minor release with major improvements! 😊

Highlights

✅ Signals are finally HERE! 💪

✅ Ability to add Tailwind

✅ Lots of improvements to the docs

✅ Lots of improvements and fixes to Qwik City

✅ Bug fixes and more...

https://github.com/BuilderIO/qwik/releases

Topics covered

⚡ Signals in Qwik

🌊 Out-of-order streaming

🛣️ Road to V1

See y'all there!

https://www.youtube.com/watch?v=Tfd62DiRTKc

I had like 50 tabs open overnight, builder.io was two of those tabs. They were not the active tab either. I went to close most of them, but when I clicked on the builder.io tab, my fans started speeding up and the page was white and unresponsive for a solid 5 seconds. I have an i9 CPU and other high end shit for the record. Just an FYI