Creating token with metaplex causing bug with webpack

[The-x-35]

Describe the bug
While trying to launch a token with metaplex on webpack shows error of fs and os dependencies not found, even when they are added. This seems to be an issue with webpack only and ignoring them wont work.

To Reproduce
Steps to reproduce the behavior:
try to launch a token with metaplex on webpack on a browser.

Expected behavior
I expected it to launch token.

Screenshots
NA

Additional context
NA

[michaelessiet]

Hi @The-x-35 , please can you share a SS of the error messages you're getting. I would like to pinpoint the particular metaplex package causing the error

[The-x-35]

@michaelessiet its not really a metaplex error but fs and os modules dont work well with webpack
u can check the issue here
https://stackoverflow.com/questions/39249237/node-cannot-find-module-fs-when-using-webpack/51669301#51669301

we cant really ignore them as then the metaplex wont work.

[michaelessiet]

I'm assuming that metaplex isn't compatible on the web/browser then? fs and os are nodejs primitives and are not available in the browser unless through polyfills

[The-x-35]

@michaelessiet Yes sir you are correct. We need to find a way to deploy tokens without them.

[michaelessiet]

Alright. Will take this up after our plugin architecture migration

[The-x-35]

@michaelessiet yeah sure.