Gatsby: Can't set webpack output.publicPath

Created on 16 Jun 2019  ·  1Comment  ·  Source: gatsbyjs/gatsby

Description

I wanted to see the file names of my css blobs in the chrome dev tools.
image
the style-loader readme states that the output.publicPath webpack property must be set. Setting it via gatsby-config.js makes gatsby develop fail.

Steps to reproduce

gatsby-node.js:

  exports.onCreateWebpackConfig = ({ stage, rules, loaders, plugins, actions }) => actions.setWebpackConfig({
    output: {
      publicPath: '/',
    },
 });

Expected result

it should set the path, and absolute paths are supposed to be generated for my css files from style-loader which i configured

Actual result

> gatsby develop

success open and validate gatsby-configs - 0.058 s
success load plugins - 1.072 s
success onPreInit - 0.009 s
success initialize cache - 0.035 s
success copy gatsby files - 0.138 s
success onPreBootstrap - 0.026 s
success source and transform nodes - 0.087 s
success building schema - 0.349 s
success createPages - 0.004 s
success createPagesStatefully - 0.082 s
success onPreExtractQueries - 0.015 s
success update schema - 0.042 s
success extract queries from components - 0.157 s
success run static queries - 0.208 s — 2/2 10.53 queries/second
success run page queries - 0.052 s — 6/6 146.57 queries/second
success write out page data - 0.011 s
success write out redirect data - 0.008 s
success Build manifest and related icons - 0.411 s
success Build manifest and related icons - 0.014 s
success onPostBootstrap - 0.476 s
⠀
info bootstrap finished - 9.560 s
⠀
error There was an error compiling the html.js component for the development server.

See our docs page on debugging HTML builds for help https://gatsby.dev/debug-html


  Error: ./.cache/gatsby-browser-entry.js
  Module not found: Error: Can't resolve 'gatsby-link' in '/.../.cac
  he'
  resolve 'gatsby-link' in '/.../.cache'
    Parsed request is a module
   @ ./.cache/gatsby-browser-entry.js 3:0-112 42:0-45:64 42:0-45:64 42:0-45:64 42:0-45:64 42:0-45:64
  42:0-45:64 42:0-45:64 42:0-45:64
   @ ./node_modules/gatsby-plugin-manifest/gatsby-ssr.js
   @ ./.cache/api-runner-ssr.js

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! [email protected] develop: `gatsby develop`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the [email protected] develop script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /.../.npm/_logs/2019-06-16T19_56_49_086Z-debug.log
error Command failed with exit code 1.

Environment

System:
OS: macOS High Sierra 10.13.6
CPU: (4) x64 Intel(R) Core(TM) i5-4260U CPU @ 1.40GHz
Shell: 5.6.2 - /usr/local/bin/zsh
Binaries:
Node: 10.15.2 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.7.0 - /usr/local/bin/npm
Languages:
Python: 2.7.15 - /usr/local/bin/python
Browsers:
Chrome: 74.0.3729.169
Safari: 12.1.1
npmPackages:
gatsby: ^2.8.6 => 2.8.6
gatsby-image: ^2.1.2 => 2.1.2
gatsby-plugin-manifest: ^2.1.1 => 2.1.1
gatsby-plugin-offline: ^2.1.1 => 2.1.1
gatsby-plugin-react-helmet: ^3.0.12 => 3.0.12
gatsby-plugin-sass: ^2.0.11 => 2.0.11
gatsby-plugin-sharp: ^2.1.3 => 2.1.3
gatsby-plugin-typescript: ^2.0.15 => 2.0.15
gatsby-source-filesystem: ^2.0.38 => 2.0.38
gatsby-transformer-sharp: ^2.1.21 => 2.1.21

question or discussion

>All comments

Hey @wildeyes

A few configurations options will be ignored if set, in order to try prevent accidental breakage. Specifically, any change to entry, output, target, or resolveLoaders will be ignored.

As documented in https://www.gatsbyjs.org/docs/actions/#setWebpackConfig (excerpt above), we do not support setting a couple of keys and output is one of them!

Closing this issue for the moment but feel free to reopen if we can help with anything else related to this.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mikestopcontinues picture mikestopcontinues  ·  3Comments

andykais picture andykais  ·  3Comments

kalinchernev picture kalinchernev  ·  3Comments

signalwerk picture signalwerk  ·  3Comments

benstr picture benstr  ·  3Comments