Yeah, I used serialport a LONG time ago - on Linux - and had huge problems figuring out which usb to use. I don’t remember exactly what the solution was, but my hunch is that it has to do with your OS
RE: Can't use the `serialport` module (building for electron)
**eslint-plugin-quasar** v1.0.0-alpha.6 Release!
- feat(rules): ‘no-legacy-properties’ - will check for properties in current components that doen’t exist any longer
- fix: if message is available, use that instead of generated message
Please read release notes for details of setting up new rule.
Radio Show - Saturday August 17, 14-15 UTC
Join us to hear the news, get some security updates and meet our special guest: Dmitrij Polianin from Moscow.
As always, we’ll be recording it and will post the links in all the usual places. Hear you later!
FYI - This post is not Spam, it is the Official Quasar Radio show.
**eslint-plugin-quasar** v1.0.0-alpha.3 Release!
Quasar is pleased to announce that there is a new ESLint plugin (eslint-plugin-quasar) available today!
Currently, this plugin will work with Users that are converting legacy Quasar to v1. If you are not doing this, then no need to install it at this time.
More rules will be added in the near future for v1 Quasar as best practices are determined. You can add an issue against the repo detailing a rule if you have the need for one or add a PR.
RE: console.log() not showing messages
@DeliciousPickle - the quasar-cli runs in a node environment, which is where the vue files are transpiled (changed) by babel and webpack to be normal html, css and js. This stuff is then sent to the brower. If you need tighter integration with node, then you will probably want to look into creating app extensions - or potentially making electron applications. All of that is covered pretty in depth in the docs.
This is the first release of the long awaited @quasar/wizard App Extension, with which you can discover all the known App Extensions (both Official and Community) (even searching if you want), choose from collections of app extensions - and most awesome of all - keep your Extensions and Quasar itself up to date. As a special highlight, we prepared an Obyte Collection for those who want to hit the ground running.
$ quasar ext add @quasar/wizard
Now get out there and make some magick!
@quasar/obyte v1.0.0-alpha.1 Release!
This is the first release of @quasar/obyte. It include the obyte.js library as well as bitcore-mnemonic, two essential libraries for working with the Obyte ecosystem.
In the next few days I will be publishing a writeup about how you can get started with this blockchain.
@quasar/qmarkdown v1.0.0-beta.18 Release!
- feat: Plug-in system for one-offs #7
- You can now extend the markdown-it processor by using the extend property (Function) that takes md instance as a parameter.
RE: [v1] What is the difference between using cli "quasar b" and "quasar d"
@chankl78 Are you saying HMR (Hot Module Replacement) is broken in your
@quasar/qcalendar v1.0.3 Release!
- fix: now hideHeader prop won’t hide header slots #25
- fix: @click:time event should pass index when column-count > than 1 #26