Move from Yarn to NPM

[aligg]

Ticket

#11

Changes

• Move from NPM to Yarn

Context for reviewers

The most interesting change is in the storybook main.js file. Magical line is {loader: 'css-loader', "options": {url: false}}, which disables url resolution. We need this b/c with the dependencies in this repo we're installing a higher version and we need to account for a breaking change from css-loader 4.0.0 around url resolution (link to changelog). This approach mirrors what next.js is doing (link) which explains why the main app was building previously but not storybook. Last piece of context, the reason this was working w/ yarn was b/c the css-loader version was for some reason a lower version.

Testing

Yay:

[sawyerh]

Thank you! Can we add an ADR for this? There wasn't one for Yarn, which made me uncertain of the original reasoning. It'd be good to document our reasoning for NPM in case a future team wants to switch to Yarn 😅

[aligg]

Thank you! Can we add an ADR for this? There wasn't one for Yarn, which made me uncertain of the original reasoning. It'd be good to document our reasoning for NPM in case a future team wants to switch to Yarn 😅

Added! First time writing one of these so any feedback welcome. Wasn't sure if we were supposed to autogenerate the new file or something, but I just did it manually after reading the MADR docs

[sawyerh]

I tested locally and successfully ran both Storybook and Next.js (including within Docker) 👍🏻