Merge cff6592c4e into 4ff1a381d1

README.md

@@ -10,7 +10,7 @@ pairing with smart people at Hashrocket.
 
 For a steady stream of TILs, [sign up for my newsletter](https://crafty-builder-6996.ck.page/e169c61186).
 
-_1434 TILs and counting..._
+_1436 TILs and counting..._
 
 ---
 
@@ -634,6 +634,7 @@ _1434 TILs and counting..._
 
 ### Next.js
 
+- [Avoid Conflicting Files](nextjs/avoid-conflicting-files.md)
 - [Create Files And Directories For Dynamic Routes](nextjs/create-files-and-directories-for-dynamic-routes.md)
 - [Define URL Redirects In The Next Config](nextjs/define-url-redirects-in-the-next-config.md)
 - [Fetch Does Not Work In API Serverless Function](nextjs/fetch-does-not-work-in-api-serverless-function.md)
@@ -1098,6 +1099,7 @@ _1434 TILs and counting..._
 
 ### RSpec
 
+- [Avoid Accidentally Disabling Pry](rspec/avoid-accidentally-disabling-pry.md)
 - [Check Specific Arguments To Received Method](rspec/check-specific-arguments-to-received-method.md)
 - [Find Minimal Set Of Tests Causing A Flicker](rspec/find-minimal-set-of-tests-causing-a-flicker.md)
 - [Format Test Results As A JSON File](rspec/format-test-results-as-a-json-file.md)

nextjs/avoid-conflicting-files.md

@@ -0,0 +1,36 @@
+# Avoid Conflicting Files
+
+When Next.js is bundling and building your project, it will get completely
+tripped up by any instance of conflicting project files. What I mean by
+conflicting project files are two JavaScript or TypeScript (or flavors of JSX
+files) that would resolve to the same thing.
+
+Here is one example where the extensions differ:
+
+```
+src/pages/welcome.tsx
+src/pages/welcome.jsx
+```
+
+Here is another example where the paths differ but the bundled result would
+conflict:
+
+```
+src/pages/welcome.tsx
+src/pages/welcome/index.tsx
+```
+
+If you have any instances of these conflicting files, you'll be presented with
+a beguiling and cryptic error message when trying to run the dev server.
+
+```
+TypeError [ERR_INVALID_ARG_TYPE]: The "to" argument must be of type string. Received undefined
+    at new NodeError (node:internal/errors:405:5)
+    at validateString (node:internal/validators:162:11)
+    at Object.relative (node:path:1191:5)
+    at Watchpack.<anonymous> (/my_app/node_modules/.pnpm/next@14.2.5_@babel+core@7.24.9_react-dom@18.3.1_react@18.3.1/node_modules/next/dist/server/lib/router-utils/setup-dev-bundler.js:381:55) {
+  code: 'ERR_INVALID_ARG_TYPE'
+}
+```
+
+One of those files needs to go. Remove one of them and you'll be good to go.

rspec/avoid-accidentally-disabling-pry.md

@@ -0,0 +1,32 @@
+# Avoid Accidentally Disabling Pry
+
+I was recently working on a test that needed to mock an environment variable in
+order to observe the behavior under test. I initially ended up with the
+following lines in a `before` block.
+
+```ruby
+before do
+  allow(ENV).to receive(:[]).and_return("")
+  allow(ENV).to receive(:[]).with("API_SERVER_URL").and_return("localhost")
+end
+```
+
+The idea was to create a "clean" `ENV` for the test and then layer in any
+relevant environment variables from there.
+
+This is a misguided approach for a couple reasons. One particular and
+hard-to-debug issue is that this mocking of `ENV` accidentally disabled Pry
+(i.e. `binding.pry`). So once I was having issues with my test, I couldn't even
+inspect the code at runtime. It would skip right past any `binding.pry`
+statement I added.
+
+What happened is that [Pry (specifically `pry-rails`) looks for
+`ENV['DISABLE_PRY_RAILS']`](https://github.com/pry/pry-rails/blob/d8d0c6d87a5b8a3e570e0c80910fb80068f3553c/lib/pry-rails.rb#L6)
+and if that value is _truthy_ then it won't require the various `pry-rails`
+modules.
+
+The first `allow` has `ENV` responding with `""` which is truthy and will
+result in Pry being disabled.
+
+A more appropriate default would be `nil`. Also consider that there are many
+ways to access `ENV`, such as `#fetch`.

ruby/find-the-min-and-max-with-a-single-call.md

@@ -21,5 +21,7 @@ at the same time when you call
 
 ```ruby
 list = [3,7,4,15,9,1,2]
+
+list.minmax
 #=> [1,15]
 ```