Closed clcrutch closed 6 years ago
See https://github.com/zurb/foundation-sites/issues/10886
We are aware of it and I am currently working on a solution.
If you want to run the unit tests, try npm install jquery@3.2.1 && npm run test
This occurs even after running npm install jquery@3.2.1
. I just want to confirm that this is still a duplicate.
Hm not sure as this is another bug as it seems. Is this the current head and what is your system setup (node, npm, ...)?
I'll try to reproduce it but I doubt that it is reproducible on my machines (node 8, npm 5).
The main machine I've been testing on has the following config:
I've also tested on a two other machines:
I apologize about the lack of details about the other two machines. I won't have access to them again for a few more hours. When have access again, I'll update with the remaining details.
guess what:
Daniel@Daniel-MSI MINGW64 ~/foundation-sites (develop)
$ npm ls jquery
foundation-sites@6.4.3 C:\Users\Daniel\foundation-sites
+-- corejs-typeahead@1.2.1
| `-- jquery@3.2.1 deduped
+-- jquery@3.2.1
`-- motion-ui@1.2.3
`-- jquery@3.2.1 deduped
jquery 3.3.1 would produce 40 failing tests. So it seems there was really a change on our side that introduced a regression in the unit tests.
I've rerun the unit tests against the v6.4.3 tag in an attempt to verify that it's not something weird in my setup.
With the v6.4.3 tag, and jQuery 3.2.1, all unit tests pass.
With the v6.4.3 tag, and jQuery 3.2.1, all unit tests pass.
Sure, it is a change in the develop branch after the 6.4.3 release. The releases are fine and the tagged revisions.
How to reproduce this bug:
npm test
What should happen:
What happened instead:
Browser(s) and Device(s) tested on:
Foundation Version(s) you are using: