-
-
Notifications
You must be signed in to change notification settings - Fork 44
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
"Cannot require a module outside a plugin" error when adding querystring to staticDependencies #42
Comments
Are you able to reproduce this problem in a simple scenario/unit test? Or there is a module that I can try to install that generate this error? |
This error occurs, when trying to install the jsonresume-theme-mocha-responsive npm package. I don't have a simple scenario, but the behaviour can be observed in KissMyResume app, when adding |
Yes, if you can create a branch and send me the steps to reproduce the problem I will appreciate. thanks! |
Hello, sorry it take me a while. Here is the branch: https://github.com/karlitos/KissMyResume/tree/static-depepndency-error The only difference to master is the added How to reproduce the error:
The error appears, when the moethod getlTheme() (app/main/theme-helpers.ts) is being called |
I found some time and updated and simplified the It's a pity I can not use this theme I developed in another of my own projects 🙁 |
I have tried to debug the issue but I'm not able to select the theme.
And then the window is blank, I don't see any |
This is happening to me on Node 14 where is was fine on Node 12. |
This is actually a followup of the issue #32. So far I was able to resolve most of the MODULE_NOT_FOUND issues with adding modules to the staticDependencies array when initializing the plugin manager. Sadly I hit a rock bottom when doing this for the querystring dependency. This results in an error: Cannot require a module outside a plugin when trying to use the module, which required the
querystring
as dependancy.Here is the output with a DEBU=* flag set:
The text was updated successfully, but these errors were encountered: