akameco / styled-spinkit Goto Github PK

Wouldn't <DoubleBounce /> like in your example be a better convention?

margin: 40px auto;

I don't want this margin , Is there a better way？

Hi, component Circle doesn't work.

Error message: Warning: Received NaN for the 'transform' attribute. If this is expected, cast the value to a string..

My component: <Circle color='#333' size={40} />.

I think you should be using import * as React from 'react';.

ERROR in [at-loader] ./node_modules/styled-spinkit/dist/ChasingDots/index.d.ts:1:8 
    TS1192: Module '"/home/cmcdragonkai/Projects/inverter-analysis/node_modules/@types/react/index"' has no default export.

Are there any issues using this with CRA or styled-component 3.x?

I am trying something very simple and it seems to crash my app every time.

import {FoldingCube} from 'styled-spinkit'

const Loading = () => {
  return (
    <LoadingArea center>
      <FoldingCube color="blue" size="30"/>
    </LoadingArea>
  )
}

The above code sends Chome into a panic and pings my CPU. Any thoughts?

• version: 0.2.0
• node version: 8.9.4
• npm (or yarn) version: npm 5.6.0

Do you want to request a feature or report a bug?:
Bug

What is the current behavior?:
The getRange function, which is used in FadingCircle, WaveLoading, and Circle, is returning an array containing one element of type Array Iterator. It appears that the addition of {loose: true} option for the babel-preset-env in the rollup config is causing the toConsumableArray function to be removed from the bundled script.

The getRange function in dist/styled-spinkit.es.js with {loose: true}:

var getRange = function getRange(n) {
  return [].concat(Array(n).keys());
};

The getRange function in dist/styled-spinkit.es.js without {loose: true}:

var getRange = function getRange(n) {
  return [].concat(toConsumableArray(Array(n).keys()));
};

What is the expected behavior?:
The getRange function should return an array of n elements with values 0 to n-1.

Suggested solution:
I don't know all the ins and outs of bundling and rollup configuration, but here are 2 changes that worked for me:

• Remove the {loose: true} key/value pair from babel-preset-env options.
  and/or
• Replace [...Array(n).keys()] with Array.from(Array(n).keys()) in the getRange function.

Hi,

First of all, thanks for this project.

I am currently working on my website on IE11, and it seems that the JS in the website crash because of this library, and in particular, the dependency round-to, they know about it ( see sindresorhus/round-to#14) , but there is no real solution because round-to is a library meant to be use in node.js, and not in a browser.
Could you tell me why use round-to instead of Math.round ?

• version:
• node version: 10.15.3
• yarn version: 1.12.1

Do you want to request a feature or report a bug?:
Bug

What is the current behavior?:
When I use styled-spinkitwith IE11, it does not work.

What is the expected behavior?:
I should be able to use the library in IE11

Suggested solution:

• Try to replace roundTo by basic Math.round
• Try another library to perform this job

I'll try to submit a PR if we find a solution.
Thanks for your help :)

This repository is up-to-date and has no outstanding updates open or pending.

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please delete the greenkeeper/initial branch in this repository, and then remove and re-add this repository to the Greenkeeper App’s white list on Github. You'll find this list on your repo or organization’s settings page, under Installed GitHub Apps.