Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build Error - Writing documentation with Docz #13662

Closed
alec-francis opened this issue Apr 26, 2019 · 2 comments
Closed

Build Error - Writing documentation with Docz #13662

alec-francis opened this issue Apr 26, 2019 · 2 comments

Comments

@alec-francis
Copy link
Contributor

Hi, I just tried following the Docz tutorial from scratch located at:
https://www.gatsbyjs.org/docs/writing-documentation-with-docz/

I received a build error:

gatsby develop
warning Configuring yargs through package.json is deprecated and will be removed in the next major release, please use the JS API instead.
success open and validate gatsby-configs — 1.289 s
success load plugins — 0.695 s
warning Configuring yargs through package.json is deprecated and will be removed in the next major release, please use the JS API instead.
success onPreInit — 0.108 s
success initialize cache — 0.004 s
success copy gatsby files — 0.331 s
success onPreBootstrap — 0.006 s
warning Configuring yargs through package.json is deprecated and will be removed in the next major release, please use the JS API instead.
success source and transform nodes — 0.339 s
success building schema — 0.229 s
warning Configuring yargs through package.json is deprecated and will be removed in the next major release, please use the JS API instead.
success createPages — 0.158 s
success createPagesStatefully — 0.068 s
success onPreExtractQueries — 0.008 s
success update schema — 0.022 s
success extract queries from components — 0.109 s
success run static queries — 0.041 s — 5/5 125.64 queries/second
success run page queries — 0.033 s — 5/5 153.95 queries/second
success write out page data — 0.038 s
success write out redirect data — 0.010 s
success Build manifest and related icons — 0.107 s
success onPostBootstrap — 0.115 s

info bootstrap finished - 6.453 s

error (node:10692) DeprecationWarning: Tapable.plugin is deprecated. Use new API on `.hooks` instead
error UNHANDLED REJECTION


  Error: You must provide the URL of lib/mappings.wasm by calling SourceMapConsumer.initialize({ 'lib/mappings.wasm': ... }) before using SourceMapConsumer

  - read-wasm.js:8 readWasm
    [my-gatsby-site-with-docz]/[react-hot-loader]/[source-map]/lib/read-wasm.js:8:13

  - wasm.js:25 wasm
    [my-gatsby-site-with-docz]/[react-hot-loader]/[source-map]/lib/wasm.js:25:16

  - source-map-consumer.js:264 BasicSourceMapConsumer.then.that
    [my-gatsby-site-with-docz]/[react-hot-loader]/[source-map]/lib/source-map-consumer.js:264:14

Any idea what could be causing this issue?

Some of my environment details:

Windows 10 Pro Version 1803
gatsby --version
2.5.12
npm --version
6.4.1
node --version
v10.15.3

package.json

{
  "name": "gatsby-starter-default",
  "private": true,
  "description": "A simple starter to get up and developing quickly with Gatsby",
  "version": "0.1.0",
  "author": "Kyle Mathews <mathews.kyle@gmail.com>",
  "dependencies": {
    "docz": "^1.0.4",
    "docz-theme-default": "^1.0.4",
    "gatsby": "^2.3.31",
    "gatsby-image": "^2.0.40",
    "gatsby-plugin-manifest": "^2.0.29",
    "gatsby-plugin-offline": "^2.0.25",
    "gatsby-plugin-react-helmet": "^3.0.12",
    "gatsby-plugin-sharp": "^2.0.35",
    "gatsby-source-filesystem": "^2.0.32",
    "gatsby-theme-docz": "^1.0.4",
    "gatsby-transformer-sharp": "^2.1.18",
    "prop-types": "^15.7.2",
    "react": "^16.8.6",
    "react-dom": "^16.8.6",
    "react-helmet": "^5.2.0"
  },
  "devDependencies": {
    "prettier": "^1.17.0"
  },
  "keywords": [
    "gatsby"
  ],
  "license": "MIT",
  "scripts": {
    "build": "gatsby build",
    "develop": "gatsby develop",
    "format": "prettier --write src/**/*.{js,jsx}",
    "start": "npm run develop",
    "serve": "gatsby serve",
    "test": "echo \"Write tests! -> https://gatsby.dev/unit-testing\""
  },
  "repository": {
    "type": "git",
    "url": "https://github.com/gatsbyjs/gatsby-starter-default"
  },
  "bugs": {
    "url": "https://github.com/gatsbyjs/gatsby/issues"
  }
}

gatsby-config.js

module.exports = {
  siteMetadata: {
    title: `Gatsby Default Starter`,
    description: `Kick off your next, great Gatsby project with this default starter. This barebones starter ships with the main Gatsby configuration files you might need.`,
    author: `@gatsbyjs`,
  },
  __experimentalThemes: [`gatsby-theme-docz`],
  plugins: [
    `gatsby-plugin-react-helmet`,
    {
      resolve: `gatsby-source-filesystem`,
      options: {
        name: `images`,
        path: `${__dirname}/src/images`,
      },
    },
    `gatsby-transformer-sharp`,
    `gatsby-plugin-sharp`,
    {
      resolve: `gatsby-plugin-manifest`,
      options: {
        name: `gatsby-starter-default`,
        short_name: `starter`,
        start_url: `/`,
        background_color: `#663399`,
        theme_color: `#663399`,
        display: `minimal-ui`,
        icon: `src/images/gatsby-icon.png`, // This path is relative to the root of the site.
      },
    },
    // this (optional) plugin enables Progressive Web App + Offline functionality
    // To learn more, visit: https://gatsby.dev/offline
    // `gatsby-plugin-offline`,
  ],
}

Feel free to let me know if you would like any further information.

Thanks

(I'll tag @LekoArts who wrote the tutorial)

@alec-francis
Copy link
Contributor Author

Update: It looks like the issue is related to Gatsby 2.3.31. I downgraded to version 2.3.30 and the project compiled successfully.

Here is the link to another issue where this is being discussed:
#13641

Best Regards

@alec-francis
Copy link
Contributor Author

I'll close this as the PR which caused this issue has been rolled back.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant