Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

\uD83D\uDDD3 Date

\uD83D\uDC65 Participants

\uD83E\uDD45 Goals

\uD83D\uDDE3 Discussion topics

Time

Item

Presenter

Notes

5-10 minutes

Social Media Icons

Gabriel Weinberg


5 minutes

Playground Beta release

Viktor Rusakov


We release Beta version of the playground, check it out here! Leave any feedback in the Paragon slack channel thread or create a github issue through this link

5 minutes

NPM workspaces in Paragon

Viktor Rusakov

Adam Stankiewicz

Paragon git repository contains several smaller packages which was sometimes a pain point for the engineers as they would need to perform same action for each of the separate package (e.g. install dependencies).

We improved that by introducing npm workspaces in the repository (basically creating a monorepo) which allows us to greatly simplify local development in Paragon.


Example improvements

Installing dependencies

As a newcomer to Paragon who wants to install the NPM dependencies, previously you’d either have to run npm install in each individual package or have knowledge of a npm run install-all NPM script we were maintaining.

Now, running npm install after cloning the repo will install NPM dependencies for all packages.

All packages are added to a single, top-level node_modules instead of each package getting its own node_modules.

Starting the docs site locally

Previously, running npm start would output a command to cd www && npm start.

With NPM workspaces, npm start runs the npm start command in the www package.

✅ Action items

  •  

⤴ Decisions

  • No labels