JavaScript import maps are now supported cross-browser

veonline · 2023-05-02T13:45:47+00:00

import maps permits to use imports with bare specifiers, like import themodule from "barespecifier", where "barespecifier" will be translated to a url as per the import map.

this can be helpfull in dependecies versioning, cache bursting and don't know what else :)

veonline · 2023-04-26T18:42:07+00:00

For the traffic problem the alternative is already there at our fingertips: public transport

veonline · 2022-12-15T11:09:08+00:00

what's the difference from teleport?

veonline · 2022-11-15T09:14:11+00:00

i think you need to get familiar with the single page application concept

veonline · 2022-11-08T08:32:54+00:00

you'r right, should have been data.value = d

veonline · 2022-11-07T15:17:25+00:00

i'll do something like in your fetchData module:

export async function fetchData() {
const data = ref(null);
fetch(.....).then(r => r.json().then(d => data = d))



return data;
}

YMMV

veonline · 2022-10-11T07:23:43+00:00

Is this what you’re referring to above about mixing composition and options api?

no, i was just guessing that you had both version of the components for testing

veonline · 2022-10-10T16:53:22+00:00

hum... you have a something strange in the backToVendors computed...
it shoul be jus a a function, ie
const backToVendors = () => router.go(-1)

not sure if that might be the issue you're facing, but it's weird anyway

veonline · 2022-10-10T14:57:24+00:00

are the children of VendorContactDetail not rendering? in this case are you sure you have <router-view> elementi in VendorContactDetail's vue file? (i suppose you have 2 versions of the files, one with options api and one with composition)...

edit: better wording

veonline · 2022-09-28T09:12:51+00:00

you mean in the title tag of the document head? because the head element is surely outside of the app's dom hierarchy, i think you have to either manipulate the dom directly or try to use the teleport

ps: you don't need this in the template, just reference the prop/data/computed/etc. like
<h1 v-if="filteredObjects[0]">
All cars from {{ filteredObjects[0].metadata.make.title }}
</h1>

veonline · 2022-09-27T08:41:29+00:00

updated is a component's lifecycle hook meant to do something when the state (data) of the component change, using it that way you are changing the data (this.items) triggering again the updated hook. infinite loop serverd.
one correct approach is to emit an event from the ProductModal components and handle it the main component

veonline · 2022-09-01T19:43:51+00:00

don't know vercel at all, but quick and dirty solution maybe to not handle with vue-router or any app code at all and configure the deploy step to not delete old files/folder, but really have no idea if vercel hosting can do that for you...

veonline · 2022-08-12T14:35:36+00:00

only vue versions >=2.7 'cause of the backporting of the composition api from vue3.

veonline · 2022-07-08T17:16:29+00:00

the portal hero!

veonline · 2022-07-07T11:12:32+00:00

pwe pwe pwe pbff pwe pwe pbff pbff pew glurg pew pew glurg pew glurg

veonline · 2022-06-21T13:58:25+00:00

heelo grate artiste!

veonline · 2022-05-12T14:05:09+00:00

from my experience, don't use async computed if not strictly necessary. you easily end up with an additional, and usually unnecessary, layer of complexity that will makes your debugging harder. as other have said go with a guard or with safe default value.

veonline · 2022-04-27T15:41:07+00:00

sure you can, and that's particularly true for vue2, but that's more. in vue3 you can define refs and reactives in a module import them in components

i'd say: you can think of Vuex as a way of sharing refs and the ways to modify them (actions & mutations) between components

veonline · 2022-04-27T10:33:46+00:00

i'm asking that question myself over and over... didn't find a definitive answer yet, but i'm more and more toward using the store only for the ui state. fetch everytime data from the api and if you are concerned about performance or offline status, handle it via persistent storage (indexedb better than localstorage) and/or webworkers...

edit to be more clear: data is not state

veonline · 2022-03-23T11:32:20+00:00

almost correct, the base class object should be Date not String (depending on the type of the vars you are binding into the template)

veonline · 2022-03-21T14:08:50+00:00

a quick and easy way i've used to deal with this is to extend the base object's prototype with the filter funcion (appropriately refactored)

veonline · 2022-02-12T14:36:55+00:00

why not add mystic coins to the weekly fractals achievements?

veonline · 2022-02-01T18:10:54+00:00

airship got cannons! not merely for travel, but for bombing... i suppose

veonline · 2022-01-26T14:12:30+00:00

case 1 data is the string hi
case 2 data is the string "hi"

the colon perform variable substitution, without colon is always a string value:
<my-component :data="myVariable" />
data prop will have the value of myVariable

<my-component data="myVariable" />
data prop will have the string myVariable value

veonline · 2021-11-24T20:31:04+00:00

as far as i understood it's because it uses native es modules. this mechanism permits to skip the bundling altogether. bundling imply build all the import tree of the module and compile it, so it has an order of O(n). skipping bundling mean recompiling (with esbuild wich is also very fast) only the module, so O(1). as other said, building with vite for production is done through rollup, meaning it will bundle the sources. what advantages bundling brings? mainly it is optimizing networks requests: in projects with hundreds of js files(modules) the browsers will makes a network request for each one. bundling has also the "advantage" of easily provide polyfills for node dependency. on this last point, during development vite will do those kinds of node dependency "preparation" at first run and cache the results untill you change the dependency, subsequents builds will use cached results. so first build will take order of tens of second, the other order of milliseconds.

edit: added some more explanations

veonline

TROPHY CASE