Fails to build with babel core version specified in package.json

[BenAttenborough]

Bug report

Node Version

12.18.3

Environment

Linux and Windows PC

Current behaviour

I'm trying to run the code locally and there seems to be a build failure when I run npm run start (this is after I did an npm install):

🚨 Build failed.
@parcel/transformer-babel: babelCore(...).loadPartialConfigAsync is not a function

And the site cannot be reached.

Suggested solution

Digging into this it looks like it is something missing in babel core which is currently using version 7.2.0. So I tired bumping the babel version to 7.14.0 and the problem went away. I can do a pull request if that helps.

[gitInLoserWereGoingShopping]

Same issue/bug encountered.
Resolved the issue by deprecating @babel/core from 7.2.0 to 7.14.0 in devDependencies of package.json

[BenAttenborough]

Same issue/bug encountered.
Resolved the issue by deprecating @babel/core from 7.2.0 to 7.14.0 in devDependencies of package.json

Ah, I said bump the version because I thought 7.14 > 7.2. Is that not the case with version numbers? Is 2 greater than 14?

[gitInLoserWereGoingShopping]

Same issue/bug encountered.
Resolved the issue by deprecating @babel/core from 7.2.0 to 7.14.0 in devDependencies of package.json

Ah, I said bump the version because I thought 7.14 > 7.2. Is that not the case with version numbers? Is 2 greater than 14?

Hey! Actually yes the first number is the primary version iteration and then each dot is like the beginning of a new tier of changes that rolls up into the first dot's version number

I like to think of it like seasons and episodes on shows we stream!
Example:
Season 2 (or Version 2) could have many episodes (or 2.01, 2.02 <- "version numbers" etc)

So then chronologically it would be:
version 7 -> episode (or patch/release) 20
vs.
Version/Season 7 -> patch/revision (episode) 14

[JackHowa]

this should be fixed by #20

Hope this unblocks people (cc @BenAttenborough)

Thanks for this course @btholt !

[JackHowa]

This is addressed in #20. Let me know if this is still occurring for you @BenAttenborough ?