I'm currently working on my Node.js library/framework. I would like to eventually publish it as FOSS software, but I would like to hinder people who change/fork my code from not giving their changes back. This would lead me to preferring a GPL-style licence over a BSD-style licence such as most Node.js-related projects I've seen use (Node.js itself, Express.js, etc.).
So my question actually boils down to two parts:
Related to the first question, what problems can arise (in terms of practical application of the licence) from publishing my software under the GPL? First, can I do it without violating the Node.js licence or the licences of the dependencies I use (I use one dependency at the moment, which is also MIT-licensed)? I assume I can, since MIT itself is permissive. Would it be a problem the other way around (If Node.js were GPL-licensed and I wanted to publish my framework under MIT)?
Bottom line, I'm trying to understand the interplay of GPL with non GPL code in non classically-linked environments, if that has ever been put to the test, in order to see whether it makes sense for me to license my code under the GPL in order to reach the above-mentioned goal.