react-select VS pkg

I decided that I wanted to use React Select for the player input, specifically React Select Creatable, which allows users to create a new option if the one that they are looking for does not exist. With this approach, if the player that the user is trying to add as one of the game's players is not already in the database, they can add the player directly from the React Select component instead of having to do this though the seperate form for adding a new player.

We actually launched our application using the AsyncCreatableSelect from react-select. However, it has a major UX flaw that is simply causing too many problems for users.

React-Select does this by default, if you don't mind losing the native select behaviour on mobile.

I recently searched for a robust, high-quality, aria conform multi-select dropdown in vanilla js. For React there is react-select or downshift, each with millions of downloads. I couldn't find a good equivalent in vanilla.

It shows that react-google-places-autocomplete is using the previous version of react-select. Let's check that previous version. Aha! The previous version is not written in TypeScript, and does not have TS types. Let's check the documentation also (always check the documentation!), and they explain how the current version was rewritten in TypeScript.

Anyone here knows how to sort react-select options in alphabetically order?

There is a closed github issue about this topic: https://github.com/JedWatson/react-select/issues/2553

react-select The Select Component for React.

I don't remember the details, and cannot find my notes on vercel/pkg. But looking at https://github.com/vercel/pkg right now I see the project has been deprecated in favour of single-executable-applications

> Standalone CLI — we haven’t worked on a standalone CLI for the new engine yet, but will absolutely have it before the v4.0 release.

This part is the most exciting to me. Given the rest of the release announcement, I'm assuming this means that it'll be built in Rust rather than embed Node. While I'm not a Rust zealot of anything, I'm very partial to not embedding Node. Particularly when it depends on using Vercel's now-abandoned pkg[1] tool.`

[1] https://github.com/vercel/pkg

The npm package called "pkg" seems to be the standard for packaging NodeJS applications

https://www.npmjs.com/package/pkg

Unfortunately you also need to bundle all your code into a single file for it to work, but you can use any bundler (webpack, parcel, etc) you want at least

Nodejs support for "single executable applications" is getting there - this issue below is preventing wider adoption at the moment:

"The single executable application feature currently only supports running a single embedded script using the CommonJS module system."

https://nodejs.org/api/single-executable-applications.html

Should be an awesome game changer for node.js when the feature gets rounded out.

Also check out vercel's `pkg`: https://github.com/vercel/pkg/issues/1291

Yes, you can. Check out pkg for a fun option, which can package up your project and Node.js into a single executable.

Further, you could experiment with the pkg tool that allows you to package up Node JS, your source, and your dependencies into one single executable for easy distribution.

package the app using https://github.com/vercel/pkg and use a smaller base image like alpine, busybox or even scratch (if possible)

Check this thread: https://github.com/vercel/pkg/issues/1685