{"id":3613,"date":"2016-04-09T18:27:22","date_gmt":"2016-04-09T18:27:22","guid":{"rendered":"http:\/\/www.garysieling.com\/blog\/?p=3613"},"modified":"2016-04-09T18:27:22","modified_gmt":"2016-04-09T18:27:22","slug":"fixing-webpacknode-error-cannot-resolve-module-fs","status":"publish","type":"post","link":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/","title":{"rendered":"Fixing webpack\/node error: cannot resolve module &#8216;fs&#8217;"},"content":{"rendered":"<p>If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell.<\/p>\n<p>The way to fix this is to remove the dependency entirely. If you want to inject a value into your Javascript files (e.g. current version number) you can pull it in from JSON file, e.g. &#8220;require(&#8216;.\/version.json&#8217;)&#8221; or have the build script depend on the git tool and inject it&#8217;s output into your Javascript files.<\/p>\n<pre lang=\"bash\">\nERROR in .\/~\/git-rev-sync\/~\/graceful-fs\/graceful-fs.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\graceful-fs\n @ .\/~\/git-rev-sync\/~\/graceful-fs\/graceful-fs.js 1:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/graceful-fs\/fs.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\graceful-fs\n @ .\/~\/git-rev-sync\/~\/graceful-fs\/fs.js 3:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/cd.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/cd.js 1:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/common.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/common.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/ls.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/ls.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/find.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/find.js 1:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/cp.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/cp.js 1:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/rm.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/rm.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/mv.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/mv.js 1:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/mkdir.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/mkdir.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/test.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/test.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/cat.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/cat.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/to.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/to.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/toEnd.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/toEnd.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/sed.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/sed.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/grep.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/grep.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/which.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/which.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/ln.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/ln.js 1:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/exec.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/exec.js 5:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/exec.js\nModule not found: Error: Cannot resolve module 'child_process' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/exec.js 6:12-36\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/chmod.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/chmod.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/touch.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/touch.js 2:9-22\n\nERROR in .\/~\/git-rev-sync\/~\/shelljs\/src\/tempdir.js\nModule not found: Error: Cannot resolve module 'fs' in D:\\projects\\image-annotation\\node_modules\\git-rev-sync\\node_modules\\shelljs\\src\n @ .\/~\/git-rev-sync\/~\/shelljs\/src\/tempdir.js 3:9-22\n\nERROR in (webpack)\/~\/node-libs-browser\/~\/constants-browserify\/constants.json\nModule parse failed: D:\\projects\\image-annotation\\node_modules\\webpack\\node_modules\\node-libs-browser\\node_modules\\constants-browserify\\constants.json Line 2: Unexpected token :\nYou may need an appropriate loader to handle this file type.\n| {\n|   \"O_RDONLY\": 0,\n|   \"O_WRONLY\": 1,\n|   \"O_RDWR\": 2,\n @ .\/~\/git-rev-sync\/~\/graceful-fs\/polyfills.js 2:16-36\n<\/pre>\n","protected":false},"excerpt":{"rendered":"<p>If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Fixing webpack\/node error: cannot resolve module &#8216;fs&#8217;&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[9],"tags":[249,302,387,393,455,592],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 4.9.9 - aioseo.com -->\n\t<meta name=\"description\" content=\"If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"gary\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/\" \/>\n\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 4.9.9\" \/>\n\t\t<meta property=\"og:locale\" content=\"en_US\" \/>\n\t\t<meta property=\"og:site_name\" content=\"Gary Sieling - Software Engineer\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"Fixing webpack\/node error: cannot resolve module \u2018fs\u2019 - Gary Sieling\" \/>\n\t\t<meta property=\"og:description\" content=\"If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2016-04-09T18:27:22+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2016-04-09T18:27:22+00:00\" \/>\n\t\t<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n\t\t<meta name=\"twitter:title\" content=\"Fixing webpack\/node error: cannot resolve module \u2018fs\u2019 - Gary Sieling\" \/>\n\t\t<meta name=\"twitter:description\" content=\"If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this\" \/>\n\t\t<script type=\"application\/ld+json\" class=\"aioseo-schema\">\n\t\t\t{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"BlogPosting\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#blogposting\",\"name\":\"Fixing webpack\\\/node error: cannot resolve module \\u2018fs\\u2019 - Gary Sieling\",\"headline\":\"Fixing webpack\\\/node error: cannot resolve module &#8216;fs&#8217;\",\"author\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/author\\\/gary\\\/#author\"},\"publisher\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/#organization\"},\"datePublished\":\"2016-04-09T18:27:22+00:00\",\"dateModified\":\"2016-04-09T18:27:22+00:00\",\"inLanguage\":\"en-US\",\"commentCount\":2,\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#webpage\"},\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#webpage\"},\"articleSection\":\"Errors, git, javascript, node, npm, react, webpack\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#breadcrumblist\",\"itemListElement\":[{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog#listItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/www.garysieling.com\\\/blog\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/category\\\/errors\\\/#listItem\",\"name\":\"Errors\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/category\\\/errors\\\/#listItem\",\"position\":2,\"name\":\"Errors\",\"item\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/category\\\/errors\\\/\",\"nextItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#listItem\",\"name\":\"Fixing webpack\\\/node error: cannot resolve module &#8216;fs&#8217;\"},\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog#listItem\",\"name\":\"Home\"}},{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#listItem\",\"position\":3,\"name\":\"Fixing webpack\\\/node error: cannot resolve module &#8216;fs&#8217;\",\"previousItem\":{\"@type\":\"ListItem\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/category\\\/errors\\\/#listItem\",\"name\":\"Errors\"}}]},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/#organization\",\"name\":\"Gary Sieling\",\"description\":\"Software Engineer\",\"url\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/\"},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/author\\\/gary\\\/#author\",\"url\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/author\\\/gary\\\/\",\"name\":\"gary\",\"image\":{\"@type\":\"ImageObject\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#authorImage\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/0be925276d848ffe98a6a9dc8cf33e67?s=96&d=identicon&r=g\",\"width\":96,\"height\":96,\"caption\":\"gary\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#webpage\",\"url\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/\",\"name\":\"Fixing webpack\\\/node error: cannot resolve module \\u2018fs\\u2019 - Gary Sieling\",\"description\":\"If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this\",\"inLanguage\":\"en-US\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/#website\"},\"breadcrumb\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/fixing-webpacknode-error-cannot-resolve-module-fs\\\/#breadcrumblist\"},\"author\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/author\\\/gary\\\/#author\"},\"creator\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/author\\\/gary\\\/#author\"},\"datePublished\":\"2016-04-09T18:27:22+00:00\",\"dateModified\":\"2016-04-09T18:27:22+00:00\"},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/\",\"name\":\"Gary Sieling\",\"description\":\"Software Engineer\",\"inLanguage\":\"en-US\",\"publisher\":{\"@id\":\"https:\\\/\\\/www.garysieling.com\\\/blog\\\/#organization\"}}]}\n\t\t<\/script>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"Fixing webpack\/node error: cannot resolve module \u2018fs\u2019 - Gary Sieling","description":"If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this","canonical_url":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"BlogPosting","@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#blogposting","name":"Fixing webpack\/node error: cannot resolve module \u2018fs\u2019 - Gary Sieling","headline":"Fixing webpack\/node error: cannot resolve module &#8216;fs&#8217;","author":{"@id":"https:\/\/www.garysieling.com\/blog\/author\/gary\/#author"},"publisher":{"@id":"https:\/\/www.garysieling.com\/blog\/#organization"},"datePublished":"2016-04-09T18:27:22+00:00","dateModified":"2016-04-09T18:27:22+00:00","inLanguage":"en-US","commentCount":2,"mainEntityOfPage":{"@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#webpage"},"isPartOf":{"@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#webpage"},"articleSection":"Errors, git, javascript, node, npm, react, webpack"},{"@type":"BreadcrumbList","@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#breadcrumblist","itemListElement":[{"@type":"ListItem","@id":"https:\/\/www.garysieling.com\/blog#listItem","position":1,"name":"Home","item":"https:\/\/www.garysieling.com\/blog","nextItem":{"@type":"ListItem","@id":"https:\/\/www.garysieling.com\/blog\/category\/errors\/#listItem","name":"Errors"}},{"@type":"ListItem","@id":"https:\/\/www.garysieling.com\/blog\/category\/errors\/#listItem","position":2,"name":"Errors","item":"https:\/\/www.garysieling.com\/blog\/category\/errors\/","nextItem":{"@type":"ListItem","@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#listItem","name":"Fixing webpack\/node error: cannot resolve module &#8216;fs&#8217;"},"previousItem":{"@type":"ListItem","@id":"https:\/\/www.garysieling.com\/blog#listItem","name":"Home"}},{"@type":"ListItem","@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#listItem","position":3,"name":"Fixing webpack\/node error: cannot resolve module &#8216;fs&#8217;","previousItem":{"@type":"ListItem","@id":"https:\/\/www.garysieling.com\/blog\/category\/errors\/#listItem","name":"Errors"}}]},{"@type":"Organization","@id":"https:\/\/www.garysieling.com\/blog\/#organization","name":"Gary Sieling","description":"Software Engineer","url":"https:\/\/www.garysieling.com\/blog\/"},{"@type":"Person","@id":"https:\/\/www.garysieling.com\/blog\/author\/gary\/#author","url":"https:\/\/www.garysieling.com\/blog\/author\/gary\/","name":"gary","image":{"@type":"ImageObject","@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#authorImage","url":"https:\/\/secure.gravatar.com\/avatar\/0be925276d848ffe98a6a9dc8cf33e67?s=96&d=identicon&r=g","width":96,"height":96,"caption":"gary"}},{"@type":"WebPage","@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#webpage","url":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/","name":"Fixing webpack\/node error: cannot resolve module \u2018fs\u2019 - Gary Sieling","description":"If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this","inLanguage":"en-US","isPartOf":{"@id":"https:\/\/www.garysieling.com\/blog\/#website"},"breadcrumb":{"@id":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/#breadcrumblist"},"author":{"@id":"https:\/\/www.garysieling.com\/blog\/author\/gary\/#author"},"creator":{"@id":"https:\/\/www.garysieling.com\/blog\/author\/gary\/#author"},"datePublished":"2016-04-09T18:27:22+00:00","dateModified":"2016-04-09T18:27:22+00:00"},{"@type":"WebSite","@id":"https:\/\/www.garysieling.com\/blog\/#website","url":"https:\/\/www.garysieling.com\/blog\/","name":"Gary Sieling","description":"Software Engineer","inLanguage":"en-US","publisher":{"@id":"https:\/\/www.garysieling.com\/blog\/#organization"}}]},"og:locale":"en_US","og:site_name":"Gary Sieling - Software Engineer","og:type":"article","og:title":"Fixing webpack\/node error: cannot resolve module \u2018fs\u2019 - Gary Sieling","og:description":"If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this","og:url":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/","article:published_time":"2016-04-09T18:27:22+00:00","article:modified_time":"2016-04-09T18:27:22+00:00","twitter:card":"summary_large_image","twitter:title":"Fixing webpack\/node error: cannot resolve module \u2018fs\u2019 - Gary Sieling","twitter:description":"If you write a React application that does server side rendering, you can get a string of errors if you try to render some server side code on the client. This can occur if you depend on something like the git-rev or git-rev-sync plugins, which require access to the shell. The way to fix this"},"aioseo_meta_data":{"post_id":"3613","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":"default","schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"limit_modified_date":false,"created":"2023-02-04 16:47:51","updated":"2026-07-06 01:44:40","ai":null,"breadcrumb_settings":null,"seo_analyzer_scan_date":null},"aioseo_breadcrumb":"<div class=\"aioseo-breadcrumbs\"><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.garysieling.com\/blog\" title=\"Home\">Home<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\t<a href=\"https:\/\/www.garysieling.com\/blog\/category\/errors\/\" title=\"Errors\">Errors<\/a>\n\t\t<\/span><span class=\"aioseo-breadcrumb-separator\">&raquo;<\/span><span class=\"aioseo-breadcrumb\">\n\t\t\tFixing webpack\/node error: cannot resolve module \u2018fs\u2019\n\t\t<\/span><\/div>","aioseo_breadcrumb_json":[{"label":"Home","link":"https:\/\/www.garysieling.com\/blog"},{"label":"Errors","link":"https:\/\/www.garysieling.com\/blog\/category\/errors\/"},{"label":"Fixing webpack\/node error: cannot resolve module &#8216;fs&#8217;","link":"https:\/\/www.garysieling.com\/blog\/fixing-webpacknode-error-cannot-resolve-module-fs\/"}],"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/posts\/3613"}],"collection":[{"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/comments?post=3613"}],"version-history":[{"count":0,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/posts\/3613\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/media?parent=3613"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/categories?post=3613"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.garysieling.com\/blog\/wp-json\/wp\/v2\/tags?post=3613"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}