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

Webpack validation error #264

Closed
ghostnumber7 opened this issue Sep 16, 2021 · 8 comments
Closed

Webpack validation error #264

ghostnumber7 opened this issue Sep 16, 2021 · 8 comments

Comments

@ghostnumber7
Copy link
Contributor

A new webpack version as just released, which makes bundle fail here with the following error:

Serverless: Could not load webpack config '/Users/mgodoy/project/serverless-bundle/src/webpack.config.js'
 
 Validation Error ----------------------------------------
 
  ValidationError: Invalid options object. Ignore Plugin has been initialized using an options object that does not match the API schema.
   - options should be one of these:
     object { resourceRegExp, contextRegExp? } | object { checkResource }
     Details:
      * options misses the property 'resourceRegExp'. Should be:
        RegExp
        -> A RegExp to test the request against.
      * options misses the property 'checkResource'. Should be:
        function
        -> A filter function for resource and context.
      at validate (/Users/mgodoy/project/serverless-bundle/node_modules/webpack/node_modules/schema-utils/dist/validate.js:105:11)
      at /Users/mgodoy/project/serverless-bundle/node_modules/webpack/lib/util/create-schema-validation.js:16:17
      at new IgnorePlugin (/Users/mgodoy/project/serverless-bundle/node_modules/webpack/lib/IgnorePlugin.js:28:3)
      at plugins (/Users/mgodoy/project/serverless-bundle/src/webpack.config.js:370:16)
      at Object.<anonymous> (/Users/mgodoy/project/serverless-bundle/src/webpack.config.js:452:12)
      at Module._compile (internal/modules/cjs/loader.js:1072:14)
      at Object.Module._extensions..js (internal/modules/cjs/loader.js:1101:10)
      at Module.load (internal/modules/cjs/loader.js:937:32)
      at Function.Module._load (internal/modules/cjs/loader.js:778:12)
      at Module.require (internal/modules/cjs/loader.js:961:19)
      at require (internal/modules/cjs/helpers.js:92:18)
      at ServerlessPlugin.validate (/Users/mgodoy/project/serverless-bundle/node_modules/serverless-webpack/lib/validate.js:152:31)
      at ServerlessPlugin.tryCatcher (/Users/mgodoy/project/serverless-bundle/node_modules/bluebird/js/release/util.js:16:23)
      at Promise._settlePromiseFromHandler (/Users/mgodoy/project/serverless-bundle/node_modules/bluebird/js/release/promise.js:547:31)
      at Promise._settlePromise (/Users/mgodoy/project/serverless-bundle/node_modules/bluebird/js/release/promise.js:604:18)
      at Promise._settlePromiseCtx (/Users/mgodoy/project/serverless-bundle/node_modules/bluebird/js/release/promise.js:641:10)
      at _drainQueueStep (/Users/mgodoy/project/serverless-bundle/node_modules/bluebird/js/release/async.js:97:12)
      at _drainQueue (/Users/mgodoy/project/serverless-bundle/node_modules/bluebird/js/release/async.js:86:9)
      at Async._drainQueues (/Users/mgodoy/project/serverless-bundle/node_modules/bluebird/js/release/async.js:102:5)
      at Immediate.Async.drainQueues [as _onImmediate] (/Users/mgodoy/project/serverless-bundle/node_modules/bluebird/js/release/async.js:15:14)
      at processImmediate (internal/timers.js:464:21)
@JBoetzkes
Copy link

I am getting the same issue with serverless bundle 5.0.1

@ekremkenter
Copy link

Anyone with any fixes or a way to avoid that?

@rogueturnip
Copy link

easiest fix is to revert to 4.4.0 until a new release.

jayair added a commit that referenced this issue Sep 17, 2021
@jayair
Copy link
Member

jayair commented Sep 17, 2021

@ghostnumber7
Copy link
Contributor Author

Thanks :)

pduchesne pushed a commit to pduchesne/serverless-bundle that referenced this issue Sep 24, 2021
@bernier
Copy link

bernier commented Oct 29, 2021

Looks like a duplicate of the issue I opened back in August #259 but that one seems to have more visibility.

I tried upgrading to 5.0.2 but I'm still having the same issue, anyone was able to solve it?

@knvpk
Copy link

knvpk commented Nov 14, 2021

Im using master and still getting this error.

@knvpk
Copy link

knvpk commented Nov 14, 2021

Looks like a duplicate of the issue I opened back in August #259 but that one seems to have more visibility.

I tried upgrading to 5.0.2 but I'm still having the same issue, anyone was able to solve it?

yes with 5.0.2 also still issue exists.

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

7 participants