Clay Diffrient

@b0rgbart3 Yeah so `error_reports` is actually an endpoint for looking at the errors in the web browser. So I should have said `/error_reports/8` which in most cases is `http://localhost:3000/error_reports/` when...

@b0rgbart3 What browser are you using to do this with?

@b0rgbart3 please replace the file `app/views/shared/terms_required.html.erb` with a different version found here for now: https://gist.github.com/claydiffrient/caeec36736eb04ae1b4e and let me know if you still have the problem.

@b0rgbart3 Could you also double check that you have run `rake canvas:compile_assets` successfully?

@b0rgbart3 with that sort of error I think the best approach would be to do this: `rm -rf node_modules && rm -rf gems/**/node_modules && npm cache clean && npm install`...

@b0rgbart3 Sorry for the delay on getting back to you on this. I've had to step away from this issue for a bit to try and get a better picture...

For now though, a simple `Setting.set('terms_required', 'false')` in the rails console should get you by.

That would be great to have. I'm working on developing an application that would have a very tight coupling as you mentioned. I really like using express for RESTful API...

That's interesting. Should I convert all references to express to make it work as well as placing it in the express grunt task?

@MarconLP, this is how my code looks: ```javascript posthog.init("", { api_host: "https://app.posthog.com", autocapture: false, capture_pageview: false, advanced_disable_feature_flags_on_first_load: true, session_recording: { maskTextSelector: ".fs-exclude", maskAllInputs: false, maskInputOptions: { password: true, }, },...