![Alex Vipond Profile](https://pbs.twimg.com/profile_images/1448772802165760000/_JMqbLoY_x96.jpg)
Alex Vipond
@AlPalVipond
Followers
571
Following
5K
Statuses
2K
I'm into web development and social impact. Working on @BetterHelp & @BaleadaToolkit. 🇺🇸 ðŸ‡ðŸ‡³
Joined April 2015
One-year update to "Rethinking Reusability in Vue"! It's now 150+ pages, exploring new frontiers in reusability with @vuejs composables. $49 at Downloadable free sample includes the table of contents, changelog, introduction, and entire first chapter.
Launched a book today! 111 pages of writing, code, and data viz, all in pursuit of Vue 3 best practices, focusing on the Vue Composition API. Download the introduction for free: Launch price is $49, marked down to $39 with a launch discount.
2
1
15
RT @devongovett: People often hold up apps like Linear as paragons of software quality. In many ways it's great – fast, pretty design, slic…
0
35
0
@sdothaney Yep if you list ^18.x.x it should work out. That's probably in your package.json already, since it's the default `npm install` behavior. I'm less sure of what happens if you lock it to an exact React version, but that's a pretty rare thing to do
0
0
1
@sdothaney Bonus 3/3 The end result is that your users/installers, who have their own bundlers, will install your package and their own preferred version of React. Their node_modules will contain one copy of React, and their bundler will ship that single shared copy.
1
0
1
@branmcconnell @vuejs Oo nice! I wonder if that'll work with portaling though—portaled elements are in the same branch of the component tree in both React & Vue, but they're in a different branch of the DOM, which is what CSS cares about. Might just be a question of applying a class to each DOM parent
1
0
1