Our great sponsors
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
Then, I noticed /usr/lib/node_modules/root/package.json. Oops, it's a package called "root". In the PKGBUILD, there was an "option" --user root, which seems to be an alternative for chown -R root:root "${pkgdir}". But, npm doesn't accept this option since npm v7. Believe it or not, npm doesn't complain about any option that it doesn't recognize. So, --user root does nothing but installing the package called root.
At first, I commented under many packages. But there were too many. And this somehow seems like spamming. Then I decided to adopt orphaned packages. I only chose the packages that have at least one vote and the upstream is not deprecated or unmaintained for years. The result is the title, and more details are in my AUR repository.
And I'm using my AUR template, which made it possible for me to adopt so many packages in a short time with problems solved.
There are some really good npm -> PKGBUILD converters like https://github.com/simon04/npm2arch
Related posts
- Unable to connect to the NPM Registry
- Building and Launching a Serverless GraphQL React Application with AWS Amplify: A Step-by-Step Guide
- Multi stage docker build failing due to some error in bcrypt, how to fix it?
- Question about CS2s demo viewer and movie features/capabilities
- Everything about package.json