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

facing build issue with webpack 5 #145

Open
akankshapatel315 opened this issue Sep 11, 2022 · 3 comments
Open

facing build issue with webpack 5 #145

akankshapatel315 opened this issue Sep 11, 2022 · 3 comments

Comments

@akankshapatel315
Copy link

No description provided.

@privateOmega
Copy link
Owner

@akankshapatel315 Could you please post some logs and other details, and if possible a sandbox as well, so I can try to replicate the issue.

@stephenasuncionDEV
Copy link

@privateOmega Here is the issue

Compiled with problems:X

ERROR in ../../node_modules/@oozcitak/url/lib/URLAlgorithm.js 6:14-28

Module not found: Error: Can't resolve 'url' in '\node_modules\@oozcitak\url\lib'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
	- install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "url": false }


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js 1:137-164

Module not found: Error: Can't resolve 'crypto' in '\node_modules\html-to-docx\dist'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "crypto": require.resolve("crypto-browserify") }'
	- install 'crypto-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "crypto": false }


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js 1:164-183

Module not found: Error: Can't resolve 'fs' in '\node_modules\html-to-docx\dist'


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js 1:183-206

Module not found: Error: Can't resolve 'path' in '\node_modules\html-to-docx\dist'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "path": require.resolve("path-browserify") }'
	- install 'path-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "path": false }


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js 1:256-283

Module not found: Error: Can't resolve 'stream' in '\node_modules\html-to-docx\dist'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "stream": require.resolve("stream-browserify") }'
	- install 'stream-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "stream": false }


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js 1:283-306

Module not found: Error: Can't resolve 'http' in '\node_modules\html-to-docx\dist'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "http": require.resolve("stream-http") }'
	- install 'stream-http'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "http": false }


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js 1:306-327

Module not found: Error: Can't resolve 'url' in '\node_modules\html-to-docx\dist'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "url": require.resolve("url/") }'
	- install 'url'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "url": false }


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js 1:358-383

Module not found: Error: Can't resolve 'https' in '\node_modules\html-to-docx\dist'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "https": require.resolve("https-browserify") }'
	- install 'https-browserify'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "https": false }


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js 1:383-406

Module not found: Error: Can't resolve 'zlib' in '\node_modules\html-to-docx\dist'

BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.

If you want to include a polyfill, you need to:
	- add a fallback 'resolve.fallback: { "zlib": require.resolve("browserify-zlib") }'
	- install 'browserify-zlib'
If you don't want to include a polyfill, you can use an empty module like this:
	resolve.fallback: { "zlib": false }


ERROR in ../../node_modules/html-to-docx/dist/html-to-docx.esm.js

Cannot read properties of undefined (reading 'module')

@ppalanisamy-storesdomain

Any update on this issue?

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

4 participants