Bump dependencies so we can build w/o resolutions

[OladapoAjala]

@jennydaman this PR fixes #238

[zrthxn]

This will not work. The task isn't just to remove that block. The problem is that this issue with preset-env causes build to fail. Now react-scripts uses a module (which I seem to have forgotten the name of) which uses another module which uses a version of preset-env that breaks our build.

[OladapoAjala]

Hello @zrthxn I didn't just remove the block, I also edited the dependencies in the yarn.lock file.

So react-scripts depends on postcss-preset-env which also depends on postcss-custom-properties which finally depends on postcss-values-parser.

I bumped the postcss-custom-properties to v10.0.0 and the postcss-values-parser to v4 which solves the problem. I have successfully built the project on my local machine without the dependency resolution in the package.json file.

[zrthxn]

You're not supposed to edit the yarn.lock file to do this. This is because your changes will get overwritten whenever a new package is installed. The lock file is meant to be just for the package manager to handle module resolution. It even says this on the top of the file.

You should instead change the versions of the react-scripts package to test and see what works.

[OladapoAjala]

That was my first approach, I upgraded react-scripts to v4. However, there are other libraries that also depend on postcss-values-parser v2.0.1 hence it didn't get updated.

Except I upgrade all the other libraries which have a common sub-dependency with react-scripts then I wouldn't have to edit the yarn.lock file.

[zrthxn]

Okay then maybe try that. Upgrade all the other libraries which have the common sub-dependency to postcss-values-parser and see if that works. If it doesn't, it's not that terrible to have resolutions, at least until the issue is fixed at the source.

[OladapoAjala]

Thanks @zrthxn for pointing that I shouldn't edit the yarn.lock file, I had thought that since it was a sub-dependency it wouldn't get affected whenever a new package is installed (I was wrong!).

I would upgrade all the other dependencies and see what happens. Thanks