fix: Module is not defined in Partition chart

[michael-s-molina]

SUMMARY

#28294 broke the Partition chart dependencies producing a module is not defined error. This PR fixes the dependencies in package-lock.json to restore the plugin.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Make sure you can create a Partition chart.

ADDITIONAL INFORMATION

• Has associated issue:
• Required feature flags:
• Changes UI
• Includes DB Migration (follow approval process in SIP-59)
  • Migration is atomic, supports rollback & is backwards-compatible
  • Confirm DB migration upgrade and downgrade tested
  • Runtime estimates and downtime expectations provided
• Introduces new feature or API
• Removes existing feature or API

[sadpandajoe]

@michael-s-molina do we know why two packages got removed?

[michael-s-molina]

@michael-s-molina do we know why two packages got removed?

If you look at the commits of #28294, you'll see that a new package-lock.json was created removing the packages.

[villebro]

@michael-s-molina do we know why two packages got removed?

If you look at the commits of #28294, you'll see that a new package-lock.json was created removing the packages.

@michael-s-molina we discussed this with Joe, and the main question was do we understand why the bump removed the critical packages? Is it possible that dependabot is bumping packages with an incorrect command, or something similar? If so, we need to fix that, as this can become very expensive over time if these automated bumps break stuff.

[michael-s-molina]

@villebro It was not a dependabot change. The last two commits were manual.

[villebro]

It was not a dependabot change. The last two commits were manual.

Oooh, now this makes sense. Thanks for clarifying.