Why is there a need for another framework? the current approach is not producing fast sites, and this problem will not disappear by waiting for a faster CPU.

Foreword

Qwik in Action

Introduction to the frontend development. Now, the responsibility of creating good or bad applications depends on you because the means available are all there.

Introduction

Overview of TypeScript. TypeScript introduced types into an untyped language like Javascript to ensure code consistency.

TypeScript

Overview of the frontend architectures. In this lesson you will understand the difference from Client Side Rendering and Multi Page Application.

Frontend architectures

Overview of the hydration. In this lesson you will understand the difference from Hydration and Island architecture/Partial Hydration.

Hydration

React Server Component. In this lesson you will understand the difference from Server Component and Client Component.

React Server Component

Qwik resumability will change the frontend ecosystem, In this lesson you will understand why is so great.

Resumability, the Qwik way

Wrap up of frontend architectures module.

Summary Chapter 2

In this lesson you will be able to understand more about performance and you will understand how improve your application with less JavaScript.

Qwik, the framework built on top of closure-extraction

Resumability is the core concept behind Qwik. In this lesson you will understand better the process.

Resumability

Code Extraction is a topic hard to master, you will understand how it works with different approaches.

Code Extraction

JSX syntax is the most famous one because of React, but what about the other frameworks, Vue, Angular?

Why Qwik use JSX syntax

Summary Chapter 3

Let's see together the fundamentals of Qwik. In this lesson you will compare Webpack and Vite.

Getting started with Qwik

The Qwik build process is so important because the resumability process requires correct and intelligent bundling.

Qwik compilation Process

Qwik CLI and amazing tool to have a great Developer Experience with Qwik.

Technical requirements to start a new Qwik application

Qwik Middleware an easy and clever way to expose your RESTful APIs or GraphQL APIs.

Middleware

Wrap up of Getting Started with Qwik module.

Summary Chapter 4

In this lesson you will learn the pillars of SEO. You will lean few new terms and metrics that can help you to measure your application.

In this lesson you will learn the some new things about SEO and crawler.

Sitemap and robots files

Partytown an amazing library to execute third scripts in the service worker.

Partytown

Core Web Vitals are so important for own application. You will learn in detail all the metrics.

Core Web Vitals

Core Web Vitals Labs Data vs Field Data. These two information are so different, let's figure out the peculiarity of those.

Labs data vs Field data

Summary Chapter 5

SEO and Core Web Vitals

There are many ways to deploy a Qwik application. You can have your own server and deploy your Qwik application easily with the Qwik CLI and integrations.

Deploy Qwik in production

Cloud solution are a good alternative for a low cost pipeline and host. Nowadays these kind of services are so smart and great, you should try them.

Cloud solutions

With different team and many developers, it's important to master branching strategies to avoid problems during your day by day.

Branching strategies

Progressive Web App approach can be an alternative to the stores. You can publish you application with a lot of benefit with PWA.

Progressive Web App

Wrap up of Deploy Qwik in Production module.

Summary Chapter 6

Style an application is so important let's see how engage your Stakeholders into this process.

Style and render data with Qwik

CSS is so huge, there are a lot of ways to style your application with Qwik, let's see them together.

CSS and Built-In Styling Methods

Tailwind is an amazing library, let's see together how master it. I will share you some tips and tricks to use Tailwind in a better way.

Tailwind CSS

In this lesson you will learn how manage data with Qwik. There are a lot of APIs to explore, let's jump into the code.

Managing data with Qwik

Summary Chapter 7

In this lesson you will learn how architect a modern frontend end application.

Creating an e-commerce with Qwik and Supabase

In this lesson you will learn the trade offs of technical decisions. I share with you some tips and tricks.

Technological spike

In this lesson you will explore Supabase. This is an amazing service to leverage your business.

Supabase for your backend

A custom authentication is too complex and risky to implement from scratch. Let's use the Supabase auth to optimize our goals.

Let's talk about the Authentication process

Summary Chapter 8

Supabase CLI an handy tool to improve consistency across environments.

Supabase CLI

Let's use the Supabase CLI to manage our database migrations and schemas.

Supabase db migrations

In this lesson you will create the e-commerce homepage with the Supabase client to read the data.

Show products on our homepage

Every e-commerce has a detail page, let's create our product detail page with Qwik.

Product Detail

Cache is really useful and in this lesson I will explain in the detail how it works. I will share my experience in this topic with some cool analogies.

Cache-control headers

Summary Chapter 9

Rendering products with Orama full text search

Let's improve out application with a useful "Add to favorites" feature.

Add a product to your favorites list

In this lesson you will learn how to use Stripe to manage your payments in a secure way.

Adding cart and checkout process with Stripe

Let's try the Supabase database function. This is an easy way to allows us to do several things and also add some logic to our procedure.

Page views tracking

A real-time database with Supabase is so simple to implement, let's build together a new functionality with this great feature.

Real-time database

Summary Chapter 10

Let's explore together the benefit of testing. In this lesson you will explore the various types of tests, Unit Test, E2E, Visual regression tests and more.

Overview of application testing

Let's discuss together how and when testing is valuable for our business. 3X Explore/Expand/Extract can help us is this reasoning.

How much testing is enough? When do I write tests?

In this lesson you will lean the Test driven development TDD flow. It's a really good practice to put in place.

Test-Driven Development (TDD)

In this lesson you will lean how test your components with Cypress.

Let's add some tests with Cypress

Do you need a Qwik component library? Qwik UI is the project for you because can give you a lot of Qwik accessible components out of the box.

Qwik UI

Summary Chapter 11

Adding tests to our Qwik application

Let's explore a bit of history of Qwik. A new framework with a great past.

Final thoughts

Qwik and React together, no problem, qwikify$ is the API to solve your problems.

qwikify$

Qwik and Astro together, no problem, @qwikdev/astro is the library to solve your problems.

Qwik inside Astro application

Qwik and micro-frontends together, no problem, out of the box Qwik can manage this scenario with no external dependencies.

Micro-frontends with Qwik

Summary chapter 12

Enter your name and email address below, then click the **"Send my free chapter"** button to get started

250+ page PDF

EPub

newline Access with Replits

All Code Samples

Discord Community Access

One-time price of $69

( the primaryDescriptionMarkdown is long - several lines, include images, as long as you want )

In this course we <headline of what we do>. <why this technology is good> but <here's how learning it is problem>. 

In <the length of these lessons> we cover <three salient points about what we cover. Your BEST points>. Its <however long it is> and comes with <these bonus features, and reasons to buy. code, etc.>

It's taught by <author name> who <credibility, reason you should listen to them>. <social proof, if you have it yet>

<then you can list other supporting stuff you want to add, anything you want here>

-------
Example:
-------

We created a free course to create your first GraphQL server (from scratch) using Node and TypeScript. TypeScript and GraphQL are a powerful combo, but there's a lot of confusing edges if you're getting it setup the first time.

In this course we cover the basics of getting TypeScript setup with Node, how GraphQL works, and how to set up a GraphQL server using Apollo server. It's two hours long, it comes with complete code examples, and we walk through the code step-by-step.

It's taught by my friend, Shopify-engineer Hassan Djirdeh and he's integrated what he's learned using GraphQL in production as an engineer at Shopify. We've already had over 1,300 students enroll and it's been getting great reviews so far.

// ... and so on

Harness Qwik Resumable Architecture for Lightning-Fast Startup Times

In this course we <headline of what we do>. <why this technology is good> but <here's how learning it is problem>. 

( the summary is short - one or two lines )

Complete Guide to Qwik

Before beginning the process of building a Qwik application and analyzing its configuration in detail, several concepts need to be introduced to ensure everyone is on the same page. It's important to understand how the process of creating an application works behind the scenes. For developers, it involves writing a normal application, but the heavy lifting is done in the build phase by looking for the 

 markers and extracting the code present in the application to isolate it into small bundles. Modern code is written with the best possible language and updated tools that allow for avoiding writing raw JavaScript code. Even for the style part, raw CSS is no longer used, but always try to find a way to speed up and make writing code enjoyable. Therefore, on the one hand, TypeScript is used for the code part and other modes for the style part, e.g., SCSS or CSS in JS.

Furthermore, when the code is stripped, the application is divided into multiple files for readability and good practice reasons. Importing from external libraries is also done to take advantage of the functionality they provide without having to reimplement the functionality from scratch. Imagine having to create an application that shows the stock market performance of the Dow Jones index in real-time with interactive graphs. A library is needed that allows for creating these graphs without much effort. If it didn't exist, it would be necessary to sit down and think about how to create these components and how to handle real-time updating with measurable variability per second. It's certainly much easier to choose the right library for your needs and take advantage of the graphics that are made available.

As good front-end developers, it is known that the browser only digests three ingredients: HTML, CSS, and JavaScript. The recipe is quite simple, but who is the chef who transforms modern and complex code into those three basic ingredients that the browser recognizes? The chef in question is called a "Bundler".

 for front-end applications for years. Indeed, when it came out with a stable version, it was immediately adopted by many because it solved a series of configuration problems. Back then, setting up a development environment was a pain. Gulp, Grunt, and Browserify are just some of the tools that were used simultaneously in the project pipelines. If these names are recognized because they, too, were fought with, sympathy is extended. But if it's the first time these names have been heard, envy is extended because it means being of the new generation.

The role of the bundler is to take all of the code and combine it into one large file, which the browser can then use to load the application. This file contains the code plus any third-party dependencies that have been imported, which sometimes might have addictions and so on. So, at the end of the process, there are static files: HTML, CSS, and Javascript. But the big problem is that this process slows down more and more as the application grows in size. This slowness is not only noticeable during the production build phase but also on a day-to-day basis. Therefore, every time a file is saved and even the smallest of changes is made, a build will be started, which will take time, and therefore there will be a wait. Working this way is very frustrating because, on the one hand, there is a need to produce code to complete tasks, but it can't be done because of these constant slowdowns. Luckily, in 2020, Evan You, the creator of Vue.js, created Vite, a bundler that, thanks to a new way of processing files, solves the problems that Webpack brought with it. Now, all frameworks are based on Vite, and Qwik is no different. Vite was chosen for its speed, but how is it different from Webpack?

---
title: Getting started with Qwik
description: Let's see together the fundamentals of Qwik. In this lesson you will compare Webpack and Vite.
---

# Getting started with Qwik

Before beginning the process of building a Qwik application and analyzing its configuration in detail, several concepts need to be introduced to ensure everyone is on the same page. It's important to understand how the process of creating an application works behind the scenes. For developers, it involves writing a normal application, but the heavy lifting is done in the build phase by looking for the `$` markers and extracting the code present in the application to isolate it into small bundles. Modern code is written with the best possible language and updated tools that allow for avoiding writing raw JavaScript code. Even for the style part, raw CSS is no longer used, but always try to find a way to speed up and make writing code enjoyable. Therefore, on the one hand, TypeScript is used for the code part and other modes for the style part, e.g., SCSS or CSS in JS.

Furthermore, when the code is stripped, the application is divided into multiple files for readability and good practice reasons. Importing from external libraries is also done to take advantage of the functionality they provide without having to reimplement the functionality from scratch. Imagine having to create an application that shows the stock market performance of the Dow Jones index in real-time with interactive graphs. A library is needed that allows for creating these graphs without much effort. If it didn't exist, it would be necessary to sit down and think about how to create these components and how to handle real-time updating with measurable variability per second. It's certainly much easier to choose the right library for your needs and take advantage of the graphics that are made available.

As good front-end developers, it is known that the browser only digests three ingredients: HTML, CSS, and JavaScript. The recipe is quite simple, but who is the chef who transforms modern and complex code into those three basic ingredients that the browser recognizes? The chef in question is called a "Bundler".

## webpack

Webpack has been the reference `bundler` for front-end applications for years. Indeed, when it came out with a stable version, it was immediately adopted by many because it solved a series of configuration problems. Back then, setting up a development environment was a pain. Gulp, Grunt, and Browserify are just some of the tools that were used simultaneously in the project pipelines. If these names are recognized because they, too, were fought with, sympathy is extended. But if it's the first time these names have been heard, envy is extended because it means being of the new generation.

The role of the bundler is to take all of the code and combine it into one large file, which the browser can then use to load the application. This file contains the code plus any third-party dependencies that have been imported, which sometimes might have addictions and so on. So, at the end of the process, there are static files: HTML, CSS, and Javascript. But the big problem is that this process slows down more and more as the application grows in size. This slowness is not only noticeable during the production build phase but also on a day-to-day basis. Therefore, every time a file is saved and even the smallest of changes is made, a build will be started, which will take time, and therefore there will be a wait. Working this way is very frustrating because, on the one hand, there is a need to produce code to complete tasks, but it can't be done because of these constant slowdowns. Luckily, in 2020, Evan You, the creator of Vue.js, created Vite, a bundler that, thanks to a new way of processing files, solves the problems that Webpack brought with it. Now, all frameworks are based on Vite, and Qwik is no different. Vite was chosen for its speed, but how is it different from Webpack?