Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Does not build with Webpack 5

See original GitHub issue

Reduced Test Case

https://github.com/jacekkarczmarczyk/fullcalendar-example-projects/tree/master/vue

git clone git@github.com:jacekkarczmarczyk/fullcalendar-example-projects.git
cd fullcalendar-example-projects/vue
yarn
yarn start

Works fine if I comment all calendar related code in the component

Bug Description

Project does not compile with webpack 5. Errors:

ERROR in ./node_modules/@fullcalendar/common/main.js 9:0-86
Module not found: Error: Can't resolve './vdom' in 'C:\cygwin64\home\PC\jacekkarczmarczyk\full-calendar-webpack-5\vue\node_modules\@fullcalendar\common'

ERROR in ./node_modules/@fullcalendar/core/main.js 6:0-16
Module not found: Error: Can't resolve './vdom' in 'C:\cygwin64\home\PC\jacekkarczmarczyk\full-calendar-webpack-5\vue\node_modules\@fullcalendar\core'

ERROR in ./node_modules/@fullcalendar/core/main.js 36:16-22
export 'render' (imported as 'render') was not found in '@fullcalendar/common' (possible exports: BASE_OPTION_DEFAULTS, BASE_OPTION_REFINERS, BaseComponent, BgEvent...

ERROR in ./node_modules/@fullcalendar/vue/dist/main.js 1:0-51
Module not found: Error: Can't resolve './FullCalendar' in 'C:\cygwin64\home\PC\jacekkarczmarczyk\full-calendar-webpack-5\vue\node_modules\@fullcalendar\vue\dist'

Issue Analytics

State:
Created 3 years ago
Reactions:7
Comments:9 (3 by maintainers)

Top GitHub Comments

3reactions

doberkoflercommented, Oct 15, 2020

@bazineta Yes, there is a workaround described in https://github.com/webpack/webpack/issues/11467

{
	test: /\.m?js$/,
	resolve: {
		fullySpecified: false
	}
}

3reactions

acerixcommented, Sep 17, 2020

Thanks, confirmed.

I get different errors in the webpack example, seems to indicate missing support for v5.

ValidationError: Invalid configuration object. Webpack has been initialized using a configuration object that does not match the API schema.
 - configuration.devtool should match pattern "^(inline-|hidden-|eval-)?(nosources-)?(cheap-(module-)?)?source-map$".
   BREAKING CHANGE since webpack 5: The devtool option is more strict.