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

Wrong webpack version causes selenium-tests to fail locally #3397

Closed
pichlermarc opened this issue Nov 8, 2022 · 1 comment · Fixed by #3456
Closed

Wrong webpack version causes selenium-tests to fail locally #3397

pichlermarc opened this issue Nov 8, 2022 · 1 comment · Fixed by #3456
Assignees
Labels
bug Something isn't working priority:p4 Bugs and spec inconsistencies which do not fall into a higher prioritization

Comments

@pichlermarc
Copy link
Member

What happened?

Selenium tests are currently not working. This is seemingly due to the config being written for webpack v5+

Steps to Reproduce

  • cd ./selenium-tests
  • npm install
  • npm run server <- this will fail

Expected Result

Server starting up so that tests can be run with npm run all:local

Actual Result

Server startup fails with:

> @opentelemetry/[email protected] server
> webpack serve --progress --port 8090 --config webpack.dev.js --hot --host 0.0.0.0

[webpack-cli] Invalid configuration object. Webpack has been initialised using a configuration object that does not match the API schema.
 - configuration.target should be one of these:
   "web" | "webworker" | "node" | "async-node" | "node-webkit" | "electron-main" | "electron-renderer" | "electron-preload" | function
   -> Environment to build for
   Details:
    * configuration.target should be one of these:
      "web" | "webworker" | "node" | "async-node" | "node-webkit" | "electron-main" | "electron-renderer" | "electron-preload"
    * configuration.target should be an instance of function

Additional Details

Can be fixed by using the following webpack versions:

    "webpack": "^5.60.0",
    "webpack-cli": "^4.10.0",
    "webpack-dev-server": "^4.5.0",
    "webpack-merge": "^5.8.0"

OpenTelemetry Setup Code

n/a

package.json

n/a

Relevant log output

see "Actual Result"
@pichlermarc pichlermarc added bug Something isn't working triage labels Nov 8, 2022
@dyladan dyladan added priority:p4 Bugs and spec inconsistencies which do not fall into a higher prioritization up-for-grabs Good for taking. Extra help will be provided by maintainers and removed triage labels Nov 8, 2022
@SaumyaBhushan
Copy link
Contributor

@pichlermarc Can you please review the changes ?

@pichlermarc pichlermarc removed the up-for-grabs Good for taking. Extra help will be provided by maintainers label Nov 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority:p4 Bugs and spec inconsistencies which do not fall into a higher prioritization
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants