New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Road to v4 🎉 #2594
base: master
Are you sure you want to change the base?
Road to v4 🎉 #2594
Conversation
|
* Recreate package.lock Some problems were created when they new commits were merged * Solve hyphens and data-uri
Tests converted: scrolltooptions, resizeobserver & clipboard
* Honestly I'm fu***** stupid More merging errors * Change tests so errors don't appear 🧠
I think I've never been so happy to see the codecov comment, because it means that the PR is finally stable :))))) (apart from appveyor's node 14) The only thing that worries me is the amount of tests deleted from the I will be busy the rest of the day and probably tomorrow, so I will read the previous PR in some days. |
Sorry, that was an error 😅 |
e956b8e
to
9b94c32
Compare
Sorry for the hard reset yesterday, I didn't have time to solve the error yesterday and it failed the tests so I hard reverted the commit (actually first time I had done it). Hope it didn't affect ongoing reviews, I'll avoid forced pushes in the future. PS: I haven't merged fda7369, but you know, it merges automatically, it will get merged when a new conflicting commit appears. |
Codecov Report
@@ Coverage Diff @@
## master #2594 +/- ##
==========================================
+ Coverage 95.18% 98.52% +3.34%
==========================================
Files 5 50 +45
Lines 166 544 +378
==========================================
+ Hits 158 536 +378
Misses 8 8
Continue to review full report at Codecov.
|
I was thinking that we may use the PR to also bump some breaking updates to some dependencies, the best of all? Most of them don't even break inside Modernizr (the irony) All packages except the mocha ones can be updated to the latest version without requiring any changes (or at least |
only reason older mocha was being used was so that the test suite could run
in older browsers, to confirm that detects were actually detecting things
…On Fri, Oct 2, 2020 at 3:43 PM Markel F. ***@***.***> wrote:
I was thinking that we may use the PR to also bump some breaking updates
to some dependencies, the best of all? Most of them don't even break inside
Modernizr (the irony)
[image: Outdated packages list]
<https://camo.githubusercontent.com/8e4a5a8835dc99802881069650ceec5f39536db3/68747470733a2f2f692e696d6775722e636f6d2f6d4b774c7330682e706e67>
All packages except the mocha ones can be updated to the latest version
without requiring any changes (or at least npm test doesn't break. I will
investigate about the mocha errors and comment any discoveries that I find.
So does anyone have any problem with updating the dependencies?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2594 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADRUBRZG4LQ6DBZXDRCDO3SIYUODANCNFSM4QPUEYXA>
.
--
patrick
|
So due to the es6 imports being used now, those browsers won't work (at least not in a build) won't they? So would that mean that we can upgrade mocha? Correct me if I'm wrong |
Id hope their compiled output would work without modules? Otherwise
modernizr looses a lot of its utility (based on its usage), since evergreen
browser features are so much easier to test
On Sat, Oct 3, 2020 at 10:11 AM Markel F. ***@***.***> wrote:
So due to the es6 imports being used now, those browsers won't work (at
least not in a build) won't they? So would that mean that we can upgrade
mocha? Correct me if I'm wrong
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2594 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADRUBQMJHSZJWSCE37DJ2LSI4WIRANCNFSM4QPUEYXA>
.
--
patrick
|
Yeah, that was my idea when I wrote the correct me if I'm wrong, I mean it wouldn't make to much sense to have tests for es5 if you require es6 to run the test. But I haven't touched too much the PR except for solving all the merge conflicts, so I'm still checking some technical details about it. But yeah, I think that rollup will help on not requiring es6. Thanks! |
Keyword 'for' in `Symbol.for` caused `Undefined identifier` error in IE8.
I had started solving the conflicts before that commit was merged
@@ -133,16 +124,16 @@ if (argv.o || argv.f) { | |||
// special case around it :[ | |||
if (prop === 'setClasses') { | |||
return 'setClasses'; | |||
} else if (_.isUndefined(obj)) { | |||
throw new Error('invalid key value name - ' + prop); | |||
} else if (typeof obj === 'undefined') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
isnt (obj === undefined ) enough these days?
@@ -39,30 +37,23 @@ var yargs = require('yargs') | |||
alias: 'uglify', | |||
describe: 'uglify/minify the output' | |||
}) | |||
.options('s', { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this option is gone for good?
|
||
if (Modernizr._config.usePrefixes) { | ||
// legacy webkit syntax (TODO:: remove when syntax not in use anymore) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so the TODO isnt valid anymore? it will never be removed?
import Modernizr from '../../src/Modernizr.js'; | ||
import createElement from '../../src/createElement.js'; | ||
import docElement from '../../src/docElement.js'; | ||
import computedStyle from '../../src/computedStyle.js'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, but would be good to have changes in the feature detects separately...
(Not really sure what you mean by this...)
Modernizr.addTest('texttrackapi', results.texttrackapi); | ||
|
||
// a more strict test for track including UI support: document.createElement('track').kind === 'subtitles' | ||
Modernizr.addTest('track', 'kind' in createElement('track')); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shouldnt this just be results.track
?
@@ -16,15 +16,20 @@ | |||
} | |||
!*/ | |||
/* DOC | |||
Detects support for the `window.postMessage` protocol for cross-document messaging. | |||
Detects support for the `self.postMessage` protocol for cross-document messaging. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
self?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it doesn't seem to make too much sense
export let textencoder = Modernizr.textencoder | ||
export let textdecoder = Modernizr.textdecoder |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is here an export let? why is that special?
"load", | ||
"mq", | ||
"prefixed", | ||
"prefixes", | ||
"prefixedCSS", | ||
"setClasses", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is that gone?
and could you document those changes (in the options) in the README too?
.reduce((acc, val) => acc.concat(val), []) | ||
.reduce((acc, val) => acc.concat(val), []) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
twice the same call to reduce?
@@ -1,338 +1,339 @@ | |||
define(['isSVG'], function(isSVG) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that would be a thing: an update to html5shiv for es6 :-)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
???
var isBrowser = typeof self !== 'undefined' && typeof self.document !== 'undefined'; | ||
export default isBrowser |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
some documentation when this should be used would be needed.
// Everyone supports fontSize | ||
expect(testProps(['fontSize'])).to.be.equal(true); | ||
expect(testProps(['fontSize'])).to.equal(true); | ||
// kebab-case should work too |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you dont like the "be"s? 🐝
Just looking for other things a found this little irony 😅 #1786 (comment) Have a good day everyone and stay safe :) |
Is this still active? What can we do to help move this along? |
Hi @niksy. Honesty, I had quite forgotten of the PR, there are merge conflicts should be easy to solve (as not too many commits have been done since). But honestly I don't really know what you could do to help apart from the top comments missing checkboxes 😅. |
This PR supersedes #2108 so it closes #2108
The objetive of the PR is to finish the work started by @patrickkettner of adapting Modernizr to es6 modules. I will try to solve all merging conflicts as they are created so the PR can be picked up by anyone easily.
Compare last Patrick's commit to this PR
TODO:
(Bold means currently working on it)
scripts/flatten-for-publishing.js