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

Update dependencies #778

Merged
merged 7 commits into from May 7, 2022
Merged

Conversation

propheel
Copy link
Contributor

@propheel propheel commented Apr 8, 2022

This bumps mapbox-gl to 1.13.2 as well as lots of other dependencies like babel, storybook, webpack and webdriverio.

As a result these:

added 2345 packages, and audited 2346 packages in 1m
38 vulnerabilities (2 low, 16 moderate, 19 high, 1 critical)

came down to these:

added 2287 packages, and audited 2288 packages in 60s
24 vulnerabilities (3 moderate, 21 high)

It could have been much better though with React 18 and Webpack 5, but Storybook is not ready yet.

Still we should have #775 covered.

Also configures selenium so it starts server automatically when running tests without the need to run it manually. Changes are reflected in Readme as well.

Open for comments!

@storybook 6.4.20 blocks most of others like: react 18, webpack 5,
and keeps lots of unnecessary dependencies due to chakra 2 dep.
- new webpack dev server options
- babel support for async functions in hooks
- new uuid import style
- automatically open browser for testing
@codesandbox-ci
Copy link

codesandbox-ci bot commented Apr 8, 2022

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 4705bf8:

Sandbox Source
maputnik Configuration

@pathmapper
Copy link
Contributor

👍

@propheel I'll have a closer look and do some manual testing.

@propheel
Copy link
Contributor Author

propheel commented Apr 9, 2022

Thank you, sir. I made a number of small decisions along the way that I haven't described, so feel free to comment and I'll also try to describe them.

One of regressions to 1.7.0 I found out is that layers cannot be dragged anymore, but it's because span was changed to button and it is not draggable (sortable?) by default. The fix is a one liner, but it's going to be a part of another PR. Or I can add it to this one if you prefer.

@pathmapper
Copy link
Contributor

pathmapper commented Apr 10, 2022

I can add it to this one if you prefer.

Looks like this is a regression to master, so please add it to this PR.

Console output when trying to drag a layer:

grafik

@propheel
Copy link
Contributor Author

Just added it, @pathmapper

this is a regression to master

Technically speaking this was introduced some time ago, so it's not a regression to master rather than to v1.7.0 as I indicated. It's just a thing I noticed when I was doing manual testing.

The fix is to use shouldCancelStart. There you can also find some description why buttons work differently than span.

@pathmapper
Copy link
Contributor

Thanks @propheel , but the issue remains - it's not possible to change the layer order by dragging:

layer_drag

@pathmapper
Copy link
Contributor

Nice change regarding running the tests 👍

For Chrome two tests are failing. Do they pass on your side?

grafik

For Firefox the tests are not running, I get

Error: Failed to create session.
[0-0] Could not start a new session. Error while creating session with the driver service. Stopping driver service: Could not start a new session. Response code 400. Message: Argument --remote-debugging-port can't be set via capabilities

Any idea how to solve this?

grafik

@propheel
Copy link
Contributor Author

propheel commented May 1, 2022

Thanks @propheel , but the issue remains - it's not possible to change the layer order by dragging:

You're right, @pathmapper . That was a side effect of new array-move lib version adding in-place move. I also fixed initial load warning of selected style.

Nice change regarding running the tests 👍

Thank you 😊

For Chrome two tests are failing. Do they pass on your side?

Yes, however with latest version of Chrome (101.0.4951.41) they get stuck at some point ("resolving host" in browser). Will investigate it. Chrome passes CI though.

For Firefox the tests are not running, I get

Error: Failed to create session.
[0-0] Could not start a new session. Error while creating session with the driver service. Stopping driver service: Could not start a new session. Response code 400. Message: Argument --remote-debugging-port can't be set via capabilities

Any idea how to solve this?

Yup, I can see the same on CI as well. Seems related to webdriverio/webdriverio#8282

@pathmapper
Copy link
Contributor

Nice work @propheel, this PR is a huge step forward 🎉

Thanks for the fixes!

also fixed initial load warning of selected style

👍

Yes, however with latest version of Chrome (101.0.4951.41) they get stuck at some point ("resolving host" in browser). Will investigate it. Chrome passes CI though.

Same on my side, since FF is passing locally and CI is passing for FF + Chrome, this should't block us from merging here :-)

Opened #779 to track this is issue.

@pathmapper pathmapper merged commit bf27a35 into maplibre:master May 7, 2022
@pathmapper pathmapper mentioned this pull request May 7, 2022
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

Successfully merging this pull request may close these issues.

None yet

2 participants