Chore/fix metadata spec name

[thescientist13]

Related Issue

N / A

Summary of Changes

1. realized spec had incorrect name

TODO

1. make an issue to better handle this global state that was causing so many issues 😮‍💨 - refactor custom element definitions being shared #24

[thescientist13]

Hmm, this doesn't fail locally? 🤔

[thescientist13]

Hmm, so when debugging in the PR run, it looks like components from other specs are coming through?

{
  metadata: [
    'wcc-counter': { instanceName: 'Counter', moduleURL: [URL] },
    'wcc-paragraph': { instanceName: 'MyParagraph', moduleURL: [URL] },
    'wcc-footer': { instanceName: 'Footer', moduleURL: [URL], hydrate: 'lazy' },
    'wcc-header': { instanceName: 'Header', moduleURL: [URL] },
    'wcc-navigation': { instanceName: 'Navigation', moduleURL: [URL] }
  ]
}
the keyyyyyssss!!!! [
  'wcc-counter',
  'wcc-paragraph',
  'wcc-footer',
  'wcc-header',
  'wcc-navigation'
]

my-paragraph comes from the children-and-slot spec. 😵

---

So I guess because of how we're declaring const deps in wcc.js and perhaps the way mocha handles loading all tests

• Isolation of Test scripts mochajs/mocha#1637
• https://stackoverflow.com/questions/34458252/how-can-i-get-mocha-to-run-my-tests-in-isolation

this may be behavior to work around? Not that I am opposed to refactoring it, but wonder why it only breaks for GitHub Actions?

[netlify]

❌ Deploy Preview for merry-caramel-524e61 failed.

Name	Link
🔨 Latest commit	01f3c0f
🔍 Latest deploy log	https://app.netlify.com/sites/merry-caramel-524e61/deploys/6279b899bc63af00086e23cf