README.md in sewing_kit-0.94.0 vs README.md in sewing_kit-0.95.0
- old
+ new
@@ -233,8 +233,26 @@
NODE_ENV=production SK_SIMULATE_PRODUCTION=1 dev run
```
Note that code changes will not be automatically recompiled in this state. After verifying production behaviour, run `bundle exec rake assets:clobber` to get back to development mode.
-### My project is using `sprockets-commenoner`, can I use sewing_kit too?
+### My project is using `sprockets-commoner`, can I use sewing_kit too?
No. sprockets-commoner uses an outdated Babel version, and is no longer compatible with sewing-kit.
+
+## sewing-kit's logs are too noisy. How can I see less of them?
+
+sewing-kit defaults to using the same `log_level` as Rails' built in logger. It can be customized this using a configuration block:
+
+```ruby
+SewingKit.configure do |config|
+ config.log_level = :warn # may be `:inherit`, `:debug`, `:info`, `:warn`, or `:error`
+end
+```
+
+### How can I set breakpoints for server rendered apps?
+
+Start your Rails server with `SK_DEBUG` set as an environment variable, and configure your Node debugger to listen on port `5858`.
+
+```bash
+SK_DEBUG=1 bundle exec rails start
+```