-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
TypeError: this[MODULE_TYPE] is not a function error caused by gatsby-plugin-netlify-cms #20234
Comments
@vai0 sharing a repo will be very helpful to get a better idea of what's not working. |
Hey @erezrokah, Thanks the the quick response. I’m currently away from my machine for the holidays so won’t be able to get what you’re requesting til after Christmas. However, so far I’ve pinned the issue down to |
Thanks @vai0 that helps.
For
as the It is odd that this happens after an update to the plugin as the removal of We might need to look at the Anyway, enjoy the holidays :) Please update when you have more information |
Yup, makes perfect sense. Would probably start with looking at the options that are being passed into the filtered out version of MiniCssExtractPlugin the build is probably looking for. For reference the version I’m upgrading from did not contain that line filtering out plugins. Happy holidays 🌲 |
package.json
gatsby-config.js
|
For what it's worth, simply removing the removal of Here's my fork: https://www.npmjs.com/package/@vai0/gatsby-plugin-netlify-cms |
Hi @vai0 do you think you could create a repo reproducing the issue? I tried using your |
@erezrokah Sorry for the delay. Unfortunately I cannot share the repo, but I will try to reproduce the issue in a public repo. Will have an update either today or tomorrow. |
@erezrokah I've gotten past the Now I am encountering several issues, which I've been able to reproduce in a fresh repo here: https://github.com/vai0/repo-css-dep-issue I've copied over the latest Issues:
If I remove all gatsby dependencies from the preview component, e.g., the Link and Layout components - it solves issue 2 and 3, but the 1st issue still persists. The way I've been able to fix this so far is by removing the removal of |
@vai0 Thanks for setting up the repo, I'll try to reproduce and update when I have more information. |
Hey @vai0, I got passed number 1 by removing the
After getting passed number 1, I still had issues with running As for number 3, it only happens in dev mode and related to the comment here: #15126 (comment). I'll open a new issue for that with a fresh repo. Update: see here for number 3 |
Hey @erezrokah, thanks for promptness. I too was also able to get past 1 after switching from |
Don't have a guess, though when I tried running |
@erezrokah will give that a shot - would you mind listing your npm and node versions? |
|
using your updates from vai0/repo-css-dep-issue#1 and running with the same node and npm versions didn't fix it, only running with yarn did the trick 😞 @KyleAMathews is npm equally supported by Gatsby, or is yarn the preferred package manager? We're running into a strange build issue that only occurs with npm and not yarn, not sure if worth going down the path of migrating our project over to yarn just to get over this particular problem |
Description
After updating to the latest
gatsby-plugin-netlify-cms
, runninggatsby build
fails and throws the following errorgatsby develop
works without issue.Looking at webpack-contrib/mini-css-extract-plugin#73, suspect it may be related
Steps to reproduce
... working on putting together a demo repo
How to Make a Minimal Reproduction: https://www.gatsbyjs.org/contributing/how-to-make-a-reproducible-test-case/
Expected result
gatsby build
complete without errorActual result
See error above
Environment
The text was updated successfully, but these errors were encountered: