arcticicestudio/styled-modern-normalize

modern-normalize.css for styled-components

styled-modern-normalize's Issues

Update to latest version

There is a modern-normalize.css version 0.5.0. And styled-components version 4.1.1 for peer dependency.

Would a PR be welcome with a version bump?

Sync to modern-normalize 0.60

0.60 was released about 6 months ago. Could the next release of this package include that with updated peer dependency for styled-components v5?

Expose used fonts via public API

Exposing used fonts via public API allows to customize and add new fonts without loosing the default fonts and fallbacks. This will include sans-serif (default text) and monospace (<code> and <pre>) fonts.

Implementation Design

It will be implemented as Array<String> to allow to easily prepend new fonts using Array.unshift().

Initial implementation

Implement the initial API for the CSS definitions based on modern-normalize version 0.4.0.

API

The package should expose the following exports:

• default export modernNormalize
• MODERN_NORMALIZE_VERSION to provide the version string
• both should be available as named exports

Update peer dependency

As v5 has been out for a bit now, the following error is raised during a package install as it's not meeting the condition.

warning " > [email protected]" has incorrect peer dependency "styled-components@^2.0.0 || ^3.2.6 || ^4.1.2".

Support for styled-components v4

Related to #4
Implemented by @azdanov in PR #5

styled-components v4 has recently been released. Details about new awesome features and performance boosts can be found in the blog post, the changelog and the migration guide.
There is now a new way to use global styles via the createGlobalStyle factory API function that returns a React.Component instead of injecting it directly like in v3 with injectGlobalStyle.

To support v4, instructions will be added to the documentation how to use it with this project. We won't change the currently exported interpolated styles to export a React component since this won't allows users to compose or override the styles and would force them to use the component as it is. It would also break the usage with v3 or lower. Users who like to use the new component-based approach can simply create a new styeled component with the new createGlobalStyle API and inject the styles imported from this library, allowing them to adjust and modify it to fit their needs.

babel-macro version?

When building a project with create-react-app(CRA), styled-components offers importing it via styled-components/macro which will seamlessly integrate with CRA's babel config without having to do anything like eject config to add your own babel config and plugin for styled-components.

I've been doing so fine, but when I brought in this package, it wasn't happy as it's importing the non-babel-macro version.