Also, it is a risk to the reputation (and maybe increase the load on support?) for fontawesome (or MUI) to have to maintain a respectable SLA.MUI X is an open-core, MIT-licensed library. Being dependent on npm is fine, but building a reliance on "smaller" private registries can be a hurdle for companies like ours. Import from it was really frustrating in the (rare) instances when their registry was down for any reason, leading to all our CI/CD pipelines failing and being unable to build the app. It is an "easier mental model" that only requires putting the key inside. They have "pro" packages that extend the features of the "free" packages. About private registryĪbout, our experience has been generally great with the private registry. ![]() But admittedly it is indeed "surprising" at first glance for developers. Your explanation here makes total sense and increased our confidence in how exactly verification is performed. Sorry in advance if this is out of place, but I'd thought sharing our experience could provide some useful food for thoughts :) About license verificationĪt first, we were a bit surprised to add the license key in the public build and were looking for confirmation that this was recommended practice. If we don't feel great about having this discussion in the open, we can move it to a private Notion page.
0 Comments
Leave a Reply. |