Outputting JS from Library projects about core HOT 3 CLOSED

@granicz I don't like 3a. (If it's any of "off"/"dll"/"none"/"" - don't output JS files.) Why just not set/null? why magic aliases?

from core.

A concrete value and null would be a valid value set for an option setting (None or Some of x), but the current setting name (JsOutput) refers to the JS output without a "nothing/null" case ("and place that into the DLL and potentially in files too") and not the optionality of the file system location. We could go with what you suggest if the setting was called "JsOutputPath", but as it is, I'd prefer to go with the original 3a clause.

from core.

After further discussion we ended up with just using null/not setting the JsOutput property in wsconfig to indicate that we don't want to write .js/.jsx files for the library project.

from core.