Perhaps this is a duplicate, but I did not see a way to install a list of extensions in the documentation.
I was writing up an idea about configuring binder with a package.json for jupyterlab npm packages. But when I thought about it, it would be kind of silly to have to parse the json so that
jupyter labextension install <package-name> could loop over the file since
npm install isn’t used.
Rather than a flat, row or comma-separated .txt file - how about a .yml file with a
labextensions: key to allow for future extensibility.
labextensions: - email@example.com - firstname.lastname@example.org.* - our-extension # could skip the * resolution until someone really needs it.