Try   HackMD

Releasing Quasar Updates

@quasar/app

  1. Merge any PR's pertaining to @quasar/app into 'dev'
  2. PR a chore(app): Bump version change with just the package.json change in containing the new version number
  3. Merge the PR
  4. Create a release in GitHub releases, in the following format:

Title: @quasar/app-v2.0.1 - remember to change the version
Tag: @quasar/app-v2.0.1 - remember to change the version
Notes:

## New
* feat(app): re-introduced quasar.conf.js > framework > components/directives for special cases (like when also using functional components which cannot be covered by auto-import feature)
* feat(app): ensure quasar.conf.js > animations does not contain duplicates

## Fixes
* fix(app): For importStrategy "auto", add quasar.conf.js > framework > config > spinner (if configured) to components list #7269 
* fix(app): Avoid some issues by specifying higher versions for deps of "@quasar/babel-preset-app" (#7266)
  1. In a nice clean Quasar repo (I have one just for pulling, then updating), do the following:
    6. Pull to get latest
    7. git status - Ensure no outstanding changes.
    8. cd app
    9. npm publish
    10. Ensure version has updated on NPM: https://www.npmjs.com/package/@quasar/app
  2. Create a forum post along the lines of:

Title: @quasar/app v2.0.2 released!
Message:

Hi All,

New update available, enjoy!

## New
* feat(app): re-introduced quasar.conf.js > framework > components/directives for special cases (like when also using functional components which cannot be covered by auto-import feature)
* feat(app): ensure quasar.conf.js > animations does not contain duplicates

## Fixes
* fix(app): For importStrategy "auto", add quasar.conf.js > framework > config > spinner (if configured) to components list #7269 
* fix(app): Avoid some issues by specifying higher versions for deps of "@quasar/babel-preset-app" (#7266)
  1. Create an announcement in the main #announcements channel on Discord, along the lines of (remembering to update the version and forum within):
quasar/app v2.0.2 released! https://forum.quasar-framework.org/topic/6332/quasar-app-v2-0-2-released
  1. Ping Scott to post social media notifications.

quasar/ui

Basically the same as QApp but you need to run yarn build in quasar/ui folder before npm publish.

Last changed by 
 
Allan Gaunt
156

Read more

La Mora - Showcase Walkthrough

First Room The main door is locked by something. Interacting with it will notify you that a keycard is required. Turn around and go through the little door. In this room there are a few interactables (steam if you jump and press E), the oxygen canister, data pad, letter on the desk at the end but the main one you need is the keycard on the desk at the end (left as you walk in). Head out the room and use the keycard to get out the door. Main Hallway Once out the door, you can head to the left and interact with the tree in a canister for some dialog. Walking that way will trigger the player to notice she's in space. On the right as you come out the main door, there is a door with a light glowing down on it. This will require you to a) Have a code and b) have walked to the left of the main door so the play knows she's in space. If you haven't triggered this dialog before interacting with the door, extra dialog will show saying she needs to look around more.

Jul 15, 2021
BEX Build Commands

With the Quasar CLI, it is incredibly easy to develop and build Browser Extension distributables. Below, we'll explain the two processes in detail. Developing Start developing a Browser Extension with just one command. $ quasar dev -m bex # ..or the longer form: $ quasar dev --mode bex

Apr 13, 2020
RFC (Request for Comments) Template

Please select your type of RFC (one or more): Put an x in the boxes that apply [x] Change ? [ ] Method ? [x] Behavior ? [x] Research ? [ ] Innovation ? Other

Mar 3, 2020
HYS # 2 - Have you seen BEX?

Feb 3, 2020
Read more from Allan Gaunt
Published on HackMD