Search the Community
Showing results for tags 'compatibility issues'.
-
Admittedly, I installed Parcel after the project was underway. However, as you can see in the screenshot, I receive error messages only in reference to conflcts with code inside GSAP modules. I love GSAP. I am having a blast. But I do not understand these compatibility issues, and I don't want to touch the code inside the GSAP modules. In addition, I also receive a MODULE NOT FOUND or a "Build Failed" error regardless of whether I use "npm" or "npx" and whether I run "npx parcel index.html", "npx parcel build"; or I use the script names in package.json as in "npx run dev (or build)". It does not seem to matter. The conflicts remain the same. I searched the docs and I reviewed the other questions in this forum. I added the code below to help resolve the resolver-default issues. It was suggested in several forums: "@parcel/resolver-default": { "packageExports": true } But it does not solve the problem. I have uploaded index.html and package.json file for this project. Please note Parcel insisted I place "type=module" before the extracted GSAP modules, or Parcel would not run. So that's not the problem, I assume. The index.html file has all the Javascript above the closing body tag. It works perfectly in my local development server and on Codepen without the build tool. Do I need a build tool? I'm new. If you have any insights or - even better - solutions, I would appreciate any feedback when you can respond. The screenshot above shows the error messages I receive. I have not seen others except as noted above. I added the Codepen link, though I have not installed parcel there. I will work on making a Codepen with the current code. Since the problem lies in the package.json file, it's probably not that helpful. to produce a second codepen. Otherwise, the problematic changes are in the uploaded documents below. (EDIT: I have now forked the functional site, pasted in the code from the dysfunctional site with Parcel, and replaced the Codepen link above). I duplicated the project before I installed the build tool. I'm glad for that! Thank you , Robert index.html package-lock.json
- 10 replies
-
Hey Guys, I'm just starting to explore Greensock animation and have faced few cross browser compatibility issues with my code. I've built an animated banner which works perfectly fine on Chrome but has the animation is laggy on Safari and its worst in Firefox. I've included the codepen url. Please check the url in different browsers and you'll see the difference. Any help would be highly appreciated.
-
Hi, I've just stared working with GS in Javascript and so far love the ease of use and its flexibility. However, after testing my animations in different browsers, I've been encountering problems with certain parts. Everything was working great in Chrome, but Safari and Firefox seems to render things differently, such as elements that are misplaced in Firefox, or some that don't even show up in Safari. Any idea what can be causing these compatibility issues? Please, check the link below: http://jsbin.com/ferin/19/edit Thank you
- 6 replies
-
- compatibility issues
- firefox
-
(and 1 more)
Tagged with: