I had problems with Now.sh too - so I just buckled down and used Digital Ocean. And for those of you interested, I wrote up a how to:

https://dev.to/nothingismagick/setup-and-serve-quasar-ssr-in-a-droplet-in-30-minutes-and-in-3-quick-and-easy-steps-49kp

Generally when I am faced with this kind issue I start at the bottom and work my way up - this means specifically making sure that node-serialport is REALLY working.

Nevertheless, from that issue there one takeaways that MIGHT help you:

• use node-serialport v6.2.2

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

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.

@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!

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.

https://obyte.org

https://github.com/quasarframework/app-extension-obyte/releases/tag/v1.0.0-alpha.1

Hi @metcarob
There are technical reasons why we are not able to stop redirecting to quasar.dev. It sounds to me like you are saying that the security team won’t issue a whitelisting ticket for quasar.dev - even though at your company you are using Quasar, which is an open-source, community based project that is free?

Not going to quibble with you, but I see only a couple solutions here:

1. Demand that secops whitelist quasar.dev as an important asset to your work. Tell them that the core team of the Quasar Framework is requesting links to their badrep blocklists.
2. Git clone the repo and build the docs locally.

$ git clone https://github.com/quasarframework/quasar
$ cd quasar/docs
$ yarn
$ quasar dev -m ssr

[edit] FYI - the quasar.dev domain processes approx. 500,000 page-views monthly.

This release addresses multiple issues that have turned up. Notably:
https://github.com/quasarframework/app-extension-typescript/releases/tag/v1.0.0-beta.1

• Linting is switched to ESLint, no longer uses TSLint
• Added optional configuration setup for VS Code and suggested Extensions

Thankyou to everyone brave enough to help us get to this point - especially @IlCallo. Next stop: Stable

Excellent