Remove environment warning #59

Activity

1. electerious

   changed the title [-]Warning: environment without a `window` object[/-] [+]Remove environment warning[/+] on Sep 11, 2020
2. electerious commented on Sep 11, 2020

   

   electerious

   on Sep 11, 2020

   Owner

   More actions

   That's fine. It's because you're building or using your modules in an environment without a window object. You can ignore it if your site is working fine 😊

   We should remove this error as it's just annoying when using SSR.
3. electerious

   added

   help wanted

   on Sep 11, 2020
4. guyhamilton commented on Sep 13, 2020

   

   guyhamilton

   on Sep 13, 2020

   Author

   More actions

   @electerious Ok cheers - thanks for your response!
5. juriadams commented on Sep 15, 2020

   

   juriadams

   on Sep 15, 2020

   More actions

   What's if the site isn't working fine? 😞

   This might be a problem related to the react-basic-scroll package, but when trying to use a variable, it's initially set to NaN and when scrolling just 1px, it sets itself to the to value. I'm pretty sure this is related to this warning message.

   Here's my config:

   public config: any = {
       from: "bottom-bottom",
       to: "top-top",
       direct: true,
       props: {
           "--r": {
               from: "0",
               to: "0.1turn",
           },
       },
   };

   And here's my implementation of the ReactBasicScroll Wrapper-Component:

   <ReactBasicScroll config={this.config}>
       <div className={styles.opener}>
           <div className={styles.wrapper}>
               <div className={styles.content} style={{ transform: "rotate(var(--r))" }}>
                   ...
               </div>
           </div>
       </div>
   </ReactBasicScroll>

   When initially opening the Page, the variable is set to NaNturn:
   

   ... and after scrolling 1px, it sets itself to 0.1turn, the to value:
   

   Do you want me to open a new Issue? I'm not sure since I suspect that this relates to this issue. :)
6. electerious commented on Sep 18, 2020

   

   electerious

   on Sep 18, 2020

   Owner

   More actions

   It's not related to this issue, but it might be worth to try from: 0 instead of from: "0". Not sure if that helps. It might also be because of the from and to values. You're currently starting your animation when the bottom of the element reaches the bottom of the viewport, and ending when the top of the element reaches the top of the viewport. This should be fine, but it might be worth to try different values.

   👍React with 👍1Reacted by Brayan