Lexiverse
Lexiverse - AI contextual reading engine for English learners. Your next article is your next review.
Practise the Year 3–6 statutory spelling words with a free, playful spelling test. Kawaii or Kakkoii manga style, works offline, and your progress stays on your device.
EducationTypeScript · CSSGitHub @euangoddardOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
A spelling test PWA for the English statutory word lists
Loading the full README.
Read the full README ↗A spelling test PWA for the English statutory word lists (Years 3 & 4 and Years 5 & 6, 100 entries each), built with Qwik City.
public/sw.js precaches every page and Qwik bundle listed in q-manifest.json.Progress and settings are stored in localStorage only — nothing leaves the device.
Word data lives in src/data/words.ts; word families such as eight / eighth count as one entry, matching the statutory lists.
Run npm run build to produce the static site in dist/. It is deployed to https://manga-spell.euans.space by .github/workflows/deploy.yml on every push to main.
This project is using Qwik with QwikCity. QwikCity is just an extra set of tools on top of Qwik to make it easier to build a full site, including directory-based routing, layouts, and more.
Inside your project, you'll see the following directory structure:
├── public/
│ └── ...
└── src/
├── components/
│ └── ...
└── routes/
└── ...
src/routes: Provides the directory-based routing, which can include a hierarchy of layout.tsx layout files, and an index.tsx file as the page. Additionally, index.ts files are endpoints. Please see the routing docs for more info.
src/components: Recommended directory for components.
public: Any static assets, like images, can be placed in the public directory. Please see the Vite public directory for more info.
Use the npm run qwik add command to add additional integrations. Some examples of integrations includes: Cloudflare, Netlify or Express Server, and the Static Site Generator (SSG).
npm run qwik add # or `yarn qwik add`
Development mode uses Vite's development server. The dev command will server-side render (SSR) the output during development.
npm start # or `yarn start`
Note: during dev mode, Vite may request a significant number of
.jsfiles. This does not represent a Qwik production build.
The preview command will create a production build of the client modules, a production build of src/entry.preview.tsx, and run a local server. The preview server is only for convenience to preview a production build locally and should not be used as a production server.
npm run preview # or `yarn preview`
The production build will generate client and server modules by running both client and server build commands. The build command will use Typescript to run a type check on the source code.
npm run build # or `yarn build`
Be sure to configure your server to serve very long cache headers for the build/**/*.js files.
Typically you'd set the Cache-Control header for those files to public, max-age=31536000, immutable.
npm run build.server