@s-molinari Thx - I’m pretty new to well…all frontend development. Right now I’m just trying to determine feasibility and looks like it is workable. I had also stumbled onto the “npm ls” command that was able to show me that most of the dependencies were “dependencies of dependencies” and not directly used. Most of the ones directly used were reasonable. Thx for the clarification.

I think I got my answer, so posting this in case anybody else wants to know. I quickly did a ‘find’ on all the LICENSE file in the node_modules folder and found 446, so not every project has one, but many do. However, after ‘grepping’ all these licenses I was able to find the words “Apache” and “MIT” hundreds of times. However, the words “GNU”, “General”, and “GPL” were nowhere to be found.

@benoitranque I realize the license for Quasar itself is MIT (which is great), but my question is regarding all the many Node.js dependencies, whether they are included after build, and whether they are MIT license compatible. Apparently there are 739 dependencies in my “node_modules” folder - not a typo.

Can Quasar be used as part of a commercial closed source app? (by closed source, I simply mean it isn’t an open source license, obviously the minified javascript is always out in the open, albeit obfuscated). Initially, I thought the answer was definitely “yes” given the MIT license, but after creating a starter project I see a HUGE number of Node.js dependencies each with its own license (I inspected some and didn’t see GPL, but didn’t look thru all of them). Will all those be included in my final project ? Or just used to build? Are all those compatible with MIT license (or BSD/Apache, not GPL,etc)? I’m new to frontend development, so sorry if this is an obvious question. Thanks!