Fix other old docs links and configure markdown link checker to ignore bot-blocked domains

ihabadham · claude · ihabadham · commit ea306325efc3 · 2025-09-22T17:56:42.000+03:00
- Add NPM domains (npmjs.org/com) to ignore list due to 403 bot protection - Add hichee.com to ignore list due to Cloudflare bot blocking - Keep c9users.io as example placeholder URL to ignore 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
diff --git a/.github/markdown-link-check-config.json b/.github/markdown-link-check-config.json
@@ -8,6 +8,15 @@
     },
     {
       "pattern": "^mailto:"
+    },
+    {
+      "pattern": "^https://www\\.npmjs\\.(org|com)"
+    },
+    {
+      "pattern": "^https://your-shared-addr\\.c9users\\.io"
+    },
+    {
+      "pattern": "^https://hichee\\.com"
     }
   ],
   "replacementPatterns": [
diff --git a/NEWS.md b/NEWS.md
@@ -21,7 +21,7 @@ _A history of the news. A few bullets at the top will also show on the [README.m
 - 2017-04-09: 8.0.0 beta work to include webpacker_lite gem has begun. See [#786](https://github.com/shakacode/react_on_rails/issues/786).
 - 2017-04-03: 6.9.3 Released! Props rendered in JSON script tag. Page size is smaller now due to less escaping!
 - 2017-03-06: Updated to Webpack v2!
-- 2017-03-02: Demo of internationalization (i18n) is live at [reactrails.com](https://www.reactrails.com/). Docs [here](docs/guides/i18n.md).
+- 2017-03-02: Demo of internationalization (i18n) is live at [reactrails.com](http://reactrails.com/). Docs [here](docs/guides/i18n.md).
 - 2017-02-28: See [discussions here on Webpacker](https://github.com/rails/webpacker/issues/139) regarding how Webpacker will allow React on Rails to avoid using the asset pipeline in the near future.
 - 2017-02-28: Upgrade to Webpack v2 or use the `--bail` option in your Webpack script for test and production builds. See the discussion on [PR #730](https://github.com/shakacode/react_on_rails/pull/730).
 - 2016-11-03: Spoke at [LA Ruby: "React on Rails: Why, What, and How?"](http://www.meetup.com/laruby/events/234825187/). [Video and pictures in this article](https://blog.shakacode.com/my-react-on-rails-talk-at-the-la-ruby-rails-meetup-november-10-2016-eaaa83aff800#.ej6h4eglp).
diff --git a/docs/api/redux-store-api.md b/docs/api/redux-store-api.md
@@ -59,7 +59,7 @@ yield
 ...
 ```
 
-Components should be created as [stateless function(al) components](https://facebook.github.io/react/docs/reusable-components.html#stateless-functions). Since you can pass in initial props via the helper `redux_store`, you do not need to pass any props directly to the component. Instead, the component hydrates by connecting to the store.
+Components should be created as [function components](https://react.dev/learn/your-first-component#defining-a-component). Since you can pass in initial props via the helper `redux_store`, you do not need to pass any props directly to the component. Instead, the component hydrates by connecting to the store.
 
 **\_comments.html.erb**
 
diff --git a/docs/getting-started.md b/docs/getting-started.md
@@ -7,7 +7,7 @@ This documentation assumes the usage of ReactOnRails with Shakapacker 7. For ins
 1. Do the quick [tutorial](./guides/tutorial.md).
 2. Add React on Rails to an existing Rails app per [the instructions](./guides/installation-into-an-existing-rails-app.md).
 3. Look at [spec/dummy](https://github.com/shakacode/react_on_rails/tree/master/spec/dummy), a simple, no DB example.
-4. Look at [github.com/shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial); it's a full-featured example live at [www.reactrails.com](http://reactrails.com).
+4. Look at [github.com/shakacode/react-webpack-rails-tutorial](https://github.com/shakacode/react-webpack-rails-tutorial); it's a full-featured example live at [reactrails.com](http://reactrails.com).
 
 ## Basic Installation
 
@@ -104,7 +104,7 @@ issue.
     <%= react_component("HelloWorld", props: { name: "Stranger" }) %>
   ```
 
-- This is what your HelloWorld.js file might contain. The railsContext is always available for any parameters that you _always_ want available for your React components. It has _nothing_ to do with the concept of the [React Context](https://reactjs.org/docs/context.html). See [Render-Functions and the RailsContext](./guides/render-functions-and-railscontext.md) for more details on this topic.
+- This is what your HelloWorld.js file might contain. The railsContext is always available for any parameters that you _always_ want available for your React components. It has _nothing_ to do with the concept of the [React Context](https://react.dev/reference/react/useContext). See [Render-Functions and the RailsContext](./guides/render-functions-and-railscontext.md) for more details on this topic.
 
   ```js
   import React from 'react';
diff --git a/docs/guides/how-react-on-rails-works.md b/docs/guides/how-react-on-rails-works.md
@@ -24,7 +24,7 @@ If you open the HTML source of any web page using React on Rails, you'll see the
 1. A script tag containing the properties of the React component, such as the registered name and any props. A JavaScript function runs after the page loads, using this data to build and initialize your React components.
 1. Additional JavaScript is placed to console-log any messages, such as server rendering errors. Note: these server-side logs can be configured only to be sent to the server logs.
 
-You can see all this on the source for [reactrails.com](https://www.reactrails.com/)
+You can see all this on the source for [reactrails.com](http://reactrails.com/)
 
 ## Building the Bundles
 
diff --git a/docs/guides/render-functions-and-railscontext.md b/docs/guides/render-functions-and-railscontext.md
@@ -8,7 +8,7 @@ use shared Redux stores, you get two params passed to your function that creates
 1. `props`: Props that you pass in the view helper of either `react_component` or `redux_store`
 2. `railsContext`: Rails contextual information, such as the current pathname. You can customize
    this in your config file. **Note**: The `railsContext` is not related to the concept of a
-   ["context" for React components](https://facebook.github.io/react/docs/context.html#how-to-use-context).
+   ["context" for React components](https://react.dev/reference/react/useContext).
 
 These parameters (`props` and `railsContext`) will be the same for client- and server-side rendering,
 except for the property `railsContext.serverSide` which tells you which one it is.
diff --git a/docs/javascript/credits.md b/docs/javascript/credits.md
@@ -4,6 +4,6 @@
 
 The origins of the project began with the need to do a rich JavaScript interface for a ShakaCode's client. The choice to use Webpack and Rails is described in [Fast Rich Client Rails Development With Webpack and the ES6 Transpiler](http://www.railsonmaui.com/blog/2014/10/03/integrating-webpack-and-the-es6-transpiler-into-an-existing-rails-project/).
 
-The gem project started with [Justin Gordon](https://github.com/justin808/) pairing with [Samnang Chhun](https://github.com/samnang) to figure out how to do server rendering with Webpack plus Rails. [Alex Fedoseev](https://github.com/alexfedoseev) then joined in. [Rob Wise](https://github.com/robwise), [Aaron Van Bokhoven](https://github.com/aaronvb), and [Andy Wang](https://github.com/yorzi) did the bulk of the generators. Many others have [contributed](https://github.com/shakacode/react_on_rails/graphs/contributors).
+The gem project started with [Justin Gordon](https://github.com/justin808/) pairing with [Samnang Chhun](https://github.com/samnang) to figure out how to do server rendering with Webpack plus Rails. [Alex Fedoseev](https://github.com/alex35mil) then joined in. [Rob Wise](https://github.com/robwise), [Aaron Van Bokhoven](https://github.com/aaronvb), and [Andy Wang](https://github.com/yorzi) did the bulk of the generators. Many others have [contributed](https://github.com/shakacode/react_on_rails/graphs/contributors).
 
 The gem was initially inspired by the [react-rails gem](https://github.com/reactjs/react-rails).
diff --git a/docs/javascript/react-and-redux.md b/docs/javascript/react-and-redux.md
@@ -2,7 +2,7 @@
 
 ## Communication Between Components
 
-See [Communicate Between Components](https://web.archive.org/web/20160527122908/https://facebook.github.io/react/tips/communicate-between-components.html).
+See [Sharing State Between Components](https://react.dev/learn/sharing-state-between-components).
 
 # Redux Reducers
 
diff --git a/docs/misc/doctrine.md b/docs/misc/doctrine.md
@@ -16,7 +16,7 @@ Besides the project objective, let's stick with the "Rails Doctrine" and keep th
 
 The React on Rails setup provides several key components related to front-end developer happiness:
 
-1. [Hot reloading of both JavaScript and CSS](https://gaearon.github.io/react-hot-loader/), using the [webpack-dev-server](https://webpack.github.io/docs/webpack-dev-server.html) package. This works for both using an [Express server](http://expressjs.com/) to load stubs for the ajax requests, as well as using a live Rails server. **Oh yes**, your Rails server can do hot reloading!
+1. [Hot reloading of both JavaScript and CSS](https://gaearon.github.io/react-hot-loader/), using the [webpack-dev-server](https://webpack.js.org/configuration/dev-server/) package. This works for both using an [Express server](http://expressjs.com/) to load stubs for the ajax requests, as well as using a live Rails server. **Oh yes**, your Rails server can do hot reloading!
 2. [CSS modules](https://github.com/css-modules/webpack-demo) which remove the madness of a global namespace for CSS. We organize our CSS (Sass, actually) right next to our JavaScript React component files. This means no more creating long class names to ensure that CSS picks up the right styles.
 3. [ES6 JavaScript](http://es6-features.org/#Constants) is a great language for client side coding, much more so than Ruby due to the asynchronous nature of UI programming.
 4. JavaScript libraries and tooling work better in the native node way, rather than via some aspect of Sprockets and the Rails Asset Pipeline. We find way less frustration this way, especially from being able to get the latest advances with the rest of the JavaScript community. Why complicated beautiful JavaScript tooling Rails asset pipeline complexity?
diff --git a/docs/outdated/rails-assets-relative-paths.md b/docs/outdated/rails-assets-relative-paths.md
@@ -48,7 +48,7 @@ query: {
 },
 ```
 
-Both examples above do the exact same thing, just using different syntaxes. For the rest of this doc we will be using the JSON object style. For more information about Webpack loaders, read [this](https://webpack.github.io/docs/using-loaders.html).
+Both examples above do the exact same thing, just using different syntaxes. For the rest of this doc we will be using the JSON object style. For more information about Webpack loaders, read [this](https://webpack.js.org/concepts/loaders/).
 
 _For the sake of this doc, we're also going to add a `resolve["alias"]` inside our webpack.config to make it easier to include our assets in our jsx files. In `resolve["alias"]`, simply add:_
 
diff --git a/docs/rails/rails_view_rendering_from_inline_javascript.md b/docs/rails/rails_view_rendering_from_inline_javascript.md
@@ -1,6 +1,6 @@
 # Using ReactOnRails in JavaScript
 
-You can easily render React components in your JavaScript with `render` method that returns a [reference to the component](https://facebook.github.io/react/docs/more-about-refs.html) (virtual DOM element).
+You can easily render React components in your JavaScript with `render` method that returns a [reference to the component](https://react.dev/reference/react-dom/render#returns) (virtual DOM element).
 
 ```js
 /**
