[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-7683":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":16,"subscribersCount":16,"size":16,"stars1d":16,"stars7d":16,"stars30d":17,"stars90d":16,"forks30d":16,"starsTrendScore":16,"compositeScore":18,"rankGlobal":10,"rankLanguage":10,"license":19,"archived":20,"fork":20,"defaultBranch":21,"hasWiki":22,"hasPages":20,"topics":23,"createdAt":10,"pushedAt":10,"updatedAt":24,"readmeContent":25,"aiSummary":26,"trendingCount":16,"starSnapshotCount":16,"syncStatus":27,"lastSyncTime":28,"discoverSource":29},7683,"better_errors","BetterErrors\u002Fbetter_errors","BetterErrors","Better error page for Rack apps","",null,"Ruby",6870,433,160,48,0,1,38.91,"MIT License",false,"master",true,[],"2026-06-12 02:01:43","[![Build Status](https:\u002F\u002Fgithub.com\u002FBetterErrors\u002Fbetter_errors\u002Fworkflows\u002FCI\u002Fbadge.svg?event=push&branch=master)](https:\u002F\u002Fgithub.com\u002FBetterErrors\u002Fbetter_errors\u002Factions?query=branch%3Amaster)\n[![Codacy Badge](https:\u002F\u002Fapi.codacy.com\u002Fproject\u002Fbadge\u002FGrade\u002F6bc3e7d6118d47e6959b16690b815909)](https:\u002F\u002Fwww.codacy.com\u002Fapp\u002FBetterErrors\u002Fbetter_errors?utm_source=github.com&utm_medium=referral&utm_content=BetterErrors\u002Fbetter_errors&utm_campaign=Badge_Grade)\n[![Test Coverage](https:\u002F\u002Fcoveralls.io\u002Frepos\u002Fgithub\u002FBetterErrors\u002Fbetter_errors\u002Fbadge.svg?branch=master)](https:\u002F\u002Fcoveralls.io\u002Fgithub\u002FBetterErrors\u002Fbetter_errors?branch=master)\n[![Gem Version](https:\u002F\u002Fimg.shields.io\u002Fgem\u002Fv\u002Fbetter_errors.svg)](https:\u002F\u002Frubygems.org\u002Fgems\u002Fbetter_errors)\n\n# Better Errors\n\nBetter Errors replaces the standard Rails error page with a much better and more useful error page. It is also usable outside of Rails in any Rack app as Rack middleware.\n\n![screenshot of Better Errors in action](https:\u002F\u002Fi.imgur.com\u002F6zBGAAb.png)\n\n## Features\n\nFor screenshots of these features, [see the wiki](https:\u002F\u002Fgithub.com\u002FBetterErrors\u002Fbetter_errors\u002Fwiki).\n\n* Full stack trace\n* Source code inspection for all stack frames (with highlighting)\n* Local and instance variable inspection\n* Live shell (REPL) on every stack frame\n* Links directly to the source line in your editor\n* Useful information in non-HTML requests\n\n## Installation\n\nAdd this to your Gemfile:\n\n```ruby\ngroup :development do\n  gem \"better_errors\"\n  gem \"binding_of_caller\"\nend\n```\n\n[`binding_of_caller`](https:\u002F\u002Fgithub.com\u002Fbanister\u002Fbinding_of_caller) is optional, but is necessary to use Better Errors' advanced features (REPL, local\u002Finstance variable inspection, pretty stack frame names).\n\n_Note: If you discover that Better Errors isn't working - particularly after upgrading from version 0.5.0 or less - be sure to set `config.consider_all_requests_local = true` in `config\u002Fenvironments\u002Fdevelopment.rb`._\n\n### Optional: Set `EDITOR`\n\nFor many reasons outside of Better Errors, you should have the `EDITOR` environment variable set to your preferred\neditor.\nBetter Errors, like many other tools, will use that environment variable to show a link that opens your\neditor to the file and line from the console.\n\nBy default the links will open TextMate-protocol links.\n\nTo see if your editor is supported or to set up a different editor, see [the wiki](https:\u002F\u002Fgithub.com\u002FBetterErrors\u002Fbetter_errors\u002Fwiki\u002FLink-to-your-editor).\n\n### Optional: Set `BETTER_ERRORS_INSIDE_FRAME`\n\nIf your application is running inside of an iframe, or if you have a Content Security Policy that disallows links\nto other protocols, the editor links will not work.\n\nTo work around this set `BETTER_ERRORS_INSIDE_FRAME=1` in the environment, and the links will include `target=_blank`,\nallowing the link to open regardless of the policy.\n\n_This works because it opens the editor from a new browser tab, escaping from the restrictions of your site._\n_Unfortunately it leaves behind an empty tab each time, so only use this if needed._\n\n## Security\n\n**NOTE:** It is *critical* you put better\\_errors only in the **development** section of your Gemfile.\n**Do NOT run better_errors in production, or on Internet-facing hosts.**\n\nYou will notice that the only machine that gets the Better Errors page is localhost, which means you get the default error page if you are developing on a remote host (or a virtually remote host, such as a Vagrant box).\nObviously, the REPL is not something you want to expose to the public, and there may be sensitive information available in the backtrace.\n\nFor more information on how to configure access, see [the wiki](https:\u002F\u002Fgithub.com\u002FBetterErrors\u002Fbetter_errors\u002Fwiki\u002FAllowing-access-to-the-console).\n\n## Usage\n\nIf you're using Rails, there's nothing else you need to do.\n\n### Using without Rails.\n\nIf you're not using Rails, you need to insert `BetterErrors::Middleware` into your middleware stack, and optionally set `BetterErrors.application_root` if you'd like Better Errors to abbreviate filenames within your application.\n\nFor instructions for your specific middleware, [see the wiki](https:\u002F\u002Fgithub.com\u002FBetterErrors\u002Fbetter_errors\u002Fwiki\u002FNon-Rails-frameworks).\n\n### Plain text requests\n\nBetter Errors will render a plain text error page  when the request is an\n`XMLHttpRequest` or when the `Accept` header does *not* include 'html'.\n\n### Unicorn, Puma, and other multi-worker servers\n\nBetter Errors works by leaving a lot of context in server process memory.\nIf you're using a web server that runs multiple \"workers\" it's likely that a second\nrequest (as happens when you click on a stack frame) will hit a different\nworker.\nThat worker won't have the necessary context in memory, and you'll see\na `Session Expired` message.\n\nIf this is the case for you, consider turning the number of workers to one (1)\nin `development`. Another option would be to use Webrick, Mongrel, Thin,\nor another single-process server as your `rails server`, when you are trying\nto troubleshoot an issue in development.\n\n### Changing the link to your editor\n\nBetter Errors includes a link to your editor for the file and line of code that is being shown.\nBy default, it uses your environment to determine which editor should be opened.\nSee [the wiki for instructions on configuring the editor](https:\u002F\u002Fgithub.com\u002FBetterErrors\u002Fbetter_errors\u002Fwiki\u002FLink-to-your-editor).\n\n\n## Set maximum variable size for inspector.\n\n```ruby\n# e.g. in config\u002Finitializers\u002Fbetter_errors.rb\n# This will stop BetterErrors from trying to render larger objects, which can cause\n# slow loading times and browser performance problems. Stated size is in characters and refers\n# to the length of #inspect's payload for the given object. Please be aware that HTML escaping\n# modifies the size of this payload so setting this limit too precisely is not recommended.  \n# default value: 100_000\nBetterErrors.maximum_variable_inspect_size = 100_000\n```\n\n## Ignore inspection of variables with certain classes.\n\n```ruby\n# e.g. in config\u002Finitializers\u002Fbetter_errors.rb\n# This will stop BetterErrors from trying to inspect objects of these classes, which can cause\n# slow loading times and unnecessary database queries. Does not check inheritance chain, use\n# strings not constants.\n# default value: ['ActionDispatch::Request', 'ActionDispatch::Response']\nBetterErrors.ignored_classes = ['ActionDispatch::Request', 'ActionDispatch::Response']\n```\n\n## Get in touch!\n\nIf you're using better_errors, I'd love to hear from you. Drop me a line and tell me what you think!\n\n## Development\n\nAfter checking out the repo, run `bundle install` to install the basic dependencies.\n\nYou can run the tests with the simplest set of dependencies using:\n\n```rb\nbundle exec rspec\n```\n\nTo run specs for each of the dependency combinations, run:\n\n```rb\nbundle exec rake test:all\n```\n\nYou can run specs for a specific dependency combination using:\n\n```rb\nBUNDLE_GEMFILE=gemfiles\u002Fpry09.gemfile bundle exec rspec\n```\n\nOn CI, the specs are run against each gemfile on each supported version of Ruby.\n\n## Contributing\n\n1. Fork it\n2. Create your feature branch (`git checkout -b my-new-feature`)\n3. Commit your changes (`git commit -am 'Add some feature'`)\n4. Push to the branch (`git push origin my-new-feature`)\n5. Create new Pull Request\n","Better Errors 是一个用于 Rack 应用的错误页面改进工具，尤其适用于 Rails 开发环境。它提供了详细的堆栈跟踪、源代码高亮显示以及在每个堆栈帧上进行实时交互式 shell（REPL）的功能，使得开发者能够更直观地查看和调试错误。此外，它还支持直接链接到编辑器中的特定代码行，方便快速定位问题所在。此项目采用 Ruby 语言编写，遵循 MIT 许可协议，非常适合需要增强开发阶段错误处理体验的 Web 应用场景。",2,"2026-06-11 03:13:46","top_language"]