Skip to content

Dup, but with more detail: Shared module is not available for eager consumption #13

Open

Description

@vandercloak

I ran into this issue when cloning the example repo + running through the readme steps.

tried with:
node v14.19.0 (npm v6.14.16)
node v16.5.0 (npm v7.19.1)

npm list dumps:
host:

host@0.1.0
├── @telenko/node-mf@0.0.5
├── bundle-loader@0.5.6
├── next@10.2.3
├── react-dom@17.0.2
├── react@17.0.2
└── webpack@5.68.0

remote:

remotelib@1.0.0
├── @babel/core@7.17.2
├── @babel/preset-react@7.16.7
├── @material-ui/core@4.12.3
├── @telenko/node-mf@0.0.5
├── babel-loader@8.2.3
├── bundle-loader@0.5.6
├── css-loader@5.2.7
├── html-webpack-plugin@5.5.0
├── react-dom@17.0.2
├── react@17.0.2
├── serve@12.0.1
├── style-loader@2.0.0
├── url-loader@4.1.1
├── webpack-cli@4.9.2
├── webpack-dev-server@3.11.3
├── webpack-merge@5.8.0
└── webpack@5.68.0

@telenko any insights or ideas what I might have wrong here?

image

Activity

  1. vandercloak commented on Feb 12, 2022

    @vandercloak
    Author

    I think I figured it out. When I use webpack minor version > 5.62 it breaks. So something in 5.63 breaks the current example. Creating a pull request to lock webpack into ~5.62.0.

    May be worth keeping this open as an issue while investigating why 5.63 breaks the current example.

  2. telenko commented on Oct 30, 2022

    @telenko
    Owner

    Hi @vandercloak, thanks! Really looks like webpack has some breaking changes, Will take a look!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions