NPM Packaging, OS Automation, Universal Styling - React Day Pre-party

We haven't expected to get back to you with another meetup so soon, but thanks to Karl Horky @karlhorky, who volunteered to co-organize our events in Berlin, we're coming back on December 1st. Next to 3 talks about Open Source, this event is also an official pre-party of React Day Berlin Conference (https://reactday.berlin), happening the day after.

Thanks to Signavio (https://www.signavio.com/), on quite a short notice, we've managed to book their cozy space to host us and 120 OS and React fans.

# Event Schedule

18:00 - Doors open - snacks, drinks, socialization
19:00 - Introduction
19:10 - "The Whys, Hows, and Whats of npm Packaging" by Juho Vepsäläinen
19:40 - "Automating Open Source Project Configuration With Mrm" by Artem Sapegin
20:10 - Short break
20:20 - "How to Support All Styles of Styling" by Jan-Felix Schwarz
20:40 - Mingle

## "The Whys, Hows, and Whats of npm Packaging" by Juho Vepsäläinen

Most of us use npm but how many understand npm packaging in detail? The purpose of this presentation is to investigate the topic and provide better idea of how to do it and also how to consume npm packages in a smart way.

About Juho (https://twitter.com/bebraw):

Juho Vepsäläinen is behind the SurviveJS effort. In addition to being a core developer of webpack, he has been active in the open source scene since the early 2000s. Blue Arrow Awards winner.

## "Automating Open Source Project Configuration With Mrm" by Artem Sapegin

We use many tools to make our life as open source developers easier: linters, test runners, continuous integration and code coverage services, etc. But maintaining configuration for these tools are far from easy, especially if you have many projects and you want them all to have similar configuration.
We've tried to solve this problem with so called scaffolding tools, like grunt-init or Yeoman generators. But if you want to update existing projects — template-based tools would overwrite a file with a new version and you’ll lose all your customizations.
Mrm, takes a different approach. It works similar to codemods: instead of a template that would overwrite everything, you’re describing in code how to modify config files or create them, if necessary, to achieve the desired state of the file.

About Artem (https://twitter.com/iamsapegin):

Frontend developer living in Berlin, passionate photographer and owner of crazy dogs. Creator of React Styleguidist.

## "How to Support All Styles of Styling" by Jan-Felix Schwarz

Today's front-end community is highly fragmented when it comes to styling. From good-old css, css modules, and inline styles to numerous css-in-js libraries—there is a range of options to choose from. As developers of open source, or inner source, UI component libraries we have to face a challenge: How can we write components that can happily co-exist with all of these approaches? This talk puts forth some best practices discovered while building a React component library shared across all different engineering teams at Signavio.

# Propose your talk

If you would like to speak at one of our next meetups, please send your talk proposals via this form (https://goo.gl/forms/ikH86P9dWFMwNzWY2), both long talks (30 min) and lightning talks are welcome. If you're not sure about your skills of public speaking, don't be shy, throw in your content ideas and we'll make sure you will get all the training needed from our speakers committee.

# Contact

If you have any questions about the React Open Source community, or willing to support us as a company and sponsor next event - reach us at [masked]