Posts made by rstoenescu

@hawkeye64 Example of package.json > devDependencies for 0.16:

"devDependencies": {
    "babel-eslint": "^8.2.2",
    "eslint": "^4.15.0",
    "eslint-config-standard": "^11.0.0",
    "eslint-friendly-formatter": "^3.0.0",
    "eslint-loader": "^2.0.0",
    "eslint-plugin-import": "^2.7.0",
    "eslint-plugin-node": "^6.0.1",
    "eslint-plugin-promise": "^3.7.0",
    "eslint-plugin-standard": "^3.0.1",
    "eslint-plugin-vue": "^4.0.0",
    "quasar-cli": "^0.16.1"
  },

To be sure you’ve installed everything correctly (my feeling is that you missed something), delete node_modules and yarn.lock/package-json.lock then yarn/npm install again.

The main problem with SW on dev mode is that it breaks HMR (Hot Module Reload) since SW caching would be in effect. If you find a clever way to make both SW and HMR happy, I’d be thrilled to integrate the solution.

@hawkeye64 it needs to be there. It’s added when quasar init-ing.

@steffanhalv

1. Do NOT change the webpack target prop. It is already configured in the right way. If you need to change it you’re doing something wrong. Please also note there’s one webpack config for the renderer process and ANOTHER separate one for the main process. Which one are you trying to change? In 99% of the cases, you don’t need to change it anyway.

2. I see that you are importing the http package, which is a node specific library, which is NOT isomorphic (doesn’t also works being run in a browser). You could use it in the main process though, but not in the renderer.

Like I mentioned in a previous post, node-loader and it’s webpack rule for renderer process (it’s currently specified only for the main process) will be available by default in Quasar CLI v0.16.2.

@jaredthirsk

1. Just a note that you won’t need the addition with Quasar CLI v0.16.2. It will also be a good idea to remove “node-loader” from your package.json, because it’s gonna get embedded into the CLI by default. The node-loader was specified only for the main process, not the renderer – I assume you are importing in the renderer process, right?
2. Since you’ve added the webpack rule, you don’t need to also specify node-loader! as prefix in your import statements.

Hi,

1. Mind that the default export is a function.
2. Are you import Socket from ‘quasar’? That ain’t right.
3. I’d rewrite your plugin:

// import WebSocket from '@uci/websocket-client'
import WebSocket from '../../uci-websocket-client/browser-client'

const ws = new WebSocket(process.env.WSS || 'ws://0.0.0.0:8090')

export ws

// leave the export, even if you don't use it
export default ({ Vue }) => {
  Vue.prototype.$socket = ws
}

Reasons for rewrite: You can then import { ws } from 'plugins/Socket' or use the Vue prototype injection (this.$socket).

Plugins are simple ES6 files. Organize them however you want. Quasar is only interested in the default export only, which should be a function with which you get access to the router, Vue object, store and app (Vue root component of your app). You can re-export stuff (through named export names) that you’ll later need.

I would recommend using sub-domains.

@jeffatef Remember that CLI v0.16 is using Webpack 4, so all your webpack plugins must be webpack 4 – usually all it takes it to upgrade to their latest version.
A common mistake when using a linter is to not update your package.json dev dependencies like babel-eslint.

The correct list of package versions (minimum versions to be correct):

"babel-eslint": "^8.2.2",
"eslint": "^4.15.0",
"eslint-config-standard": "^11.0.0",
"eslint-friendly-formatter": "^3.0.0",
"eslint-loader": "^2.0.0",
"eslint-plugin-import": "^2.7.0",
"eslint-plugin-node": "^6.0.1",
"eslint-plugin-promise": "^3.7.0",
"eslint-plugin-standard": "^3.0.1",
"eslint-plugin-vue": "^4.0.0",

@sweetyy Make sure you are editing the right src/index.template.html file. It is guaranteed that the CLI doesn’t complain for nothing.

@hawkeye64 said in Quasar v0.16 & CLI v0.16 are out!:

1. You shouldn’t be required to install babel transform plugins. And they should definitely not appear in your package.json. It’s already in the CLI. Other than the linting packages, you should not have any babel related packages there.
2. Remember CLI v0.16 uses Webpack 4, so make sure to use the latest version of any webpack plugins that you have added.
3. If the CLI detects the old babel 6 .babelrc syntax, then it replaces the file with an updated one. If you wanna change it, change the modified file AND make sure it’s babel 7 compliant.
4. If you got past the previous points and it still doesn’t works, delete node_modules and yarn.lock/package-lock.json and yarn/npm install again. But very important, don’t try to install babel stuff in your project (other than babel-eslint if you’re using the linter).

@fuxic SSR is finally under works as we speak. Good progress too.

Hi,

Don’t use subdirectories to deploy your PWA, even if you set your publicPath correctly.

Hi,

Sorry for the late reply. Worked till 10.30 in the morning and today I didn’t feel good at all. Let’s connect tomorrow (24th) on Discord. It will be easier to help you.
Thanks for backing up Quasar on Patreon!

-Razvan

Released Quasar CLI v0.16.1 – updates to newly quasar-extras v2.0.1 package which fixes an issue with Roboto font. Enjoy!

What you did sounds ok.

We are happy to announce new releases for Quasar packages.
I you enjoy the productivity of your work using Quasar, please consider becoming a backer if you aren’t already (https://www.patreon.com/quasarframework). It makes sense, since this helps us grow Quasar and it ensures your Quasar projects will receive the enhancements & bug fixes they require.
Enjoy the new release!

The difference between Quasar v0.15.x and v0.16 is minimal. No big breaking changes as you can see below. The only reason for bumping Quasar’s version is to maintain consistency (same major + minor version) with Quasar CLI (which got an important update: webpack 4, babel 7, Workbox, electron-builder support, ionicons v4 and many more).

Upgrading from v0.15.x should be seamless if you are using Quasar CLI – which will guide you to do some minor changes to your project folder. Note that Ionicons v4 has breaking changes, so if you are using it in your project, then you need to update each such icon to its new name.

Quasar v0.16

Breaking Changes

• QIcon: removed “mat” & “ios” props for performance reasons (use :name="$q.theme === 'mat' ? val : otherVal" instead)
• Removed utils > dom > viewport() method (use window.innerHeight/innerWidth instead)
• Updated Quasar ionicons set to Ionicons v4 – compatible with quasar-extras@2.0

New

• [Request] QBtn router handling (“to” and “replace” props) #2058
• Improved perf for utils > event by removing legacy IE < 11 code
• QFab “icon” prop is now optional

Fixes

• LayoutDrawer mini mode: still animating when hidden #2059

Quasar CLI v0.16

Your website/app will build much faster!

Dependency updates

• Quasar v0.16.0
• Webpack v4 (instead of v3)
• vue-loader v15
• Babel v7 (instead of v6)
• Workbox (instead of sw-precache-plugin)
• electron-builder support
• quasar-extras v2 (instead of v1)

Other changes

• Greatly improved rebuild time: babel caches compiled assets; tweaked UglifyJs config to slightly build faster and also take care of iOS quirks
• Use developer’s preferred node package manager (Yarn/NPM - Yarn is preferred) instead of always relying on NPM
• Removed node-notifier since it was hogging memory in some scenarios and it couldn’t be fixed
• Closing the electron window when developing makes Quasar CLI exit (as it should)
• Wrote some webpack plugins in order to simplify src/index.template.html (a lot of tags are no longer necessary; the html file is very simple now)
• Prevent webpack from injecting useless polyfills (like setImmediate from vue source code) and mocks to Node native modules (like “fs”, “net”, …)

Quasar Extras v2.0

vue-cli-plugin-quasar v1.7

Upgrade to using Quasar v0.16 instead of v0.15.

Fixing a jsFiddle compliancy issue.

One more important fix for QTable (regarding filter when using server-side data) and a new feature for QSlideTransition (show/hide Vue events)

Release notes

Hi,

Please update to CLI v0.15.17 if you are using Quasar v0.15.11 because of an important regression fix:

• v0.15.11 - QDatetime/QColor not setting value when on mobile #2047

Thank you.

We are very proud and honoured to now be sponsored by Taylored Technology (platinum sponsor) also.

As always, thanks to all backers! We can’t push Quasar forward without you!

If you haven’t already, please take a look at our Patreon campaign. Every cent really counts! You’ll also get access to the special #patreons-help-only Discord channel for priority help.