Sure, it's a fine approach, although there's not much advantage of using JSON (a data serialization format that happens to be a subset of JavaScript) over using plain old JavaScript.
How you do it depends a lot on your current architecture. In the very simplest case, you could just inject it into your HTML before any of your other JavaScript is loaded:
<script>
window.AppConfiguration = {
businessRules: {
dateRanges: // ...
}
};
</script>
...then in your other scripts you can access window.AppConfiguration
to get your configuration values.
If you're already using something like RequireJS or Browserify, though, you might create a module instead:
// app/configuration.js
// RequireJS style
define({
businessRules: { ... }
});
// Node.js/Browserify style
module.exports = {
businessRules: { ... }
}
Then you can just do var appConfig = require('app/configuration');
and be on your way. This also has advantages with regard to testing and build tools.