Dylan Greene

I'm proposing taking advantage of lazy loading but doing it in Grunt instead of in the tasks. This removes the responsibility from the task developers, at the cost of backwards...

Results of spending too much time trying to figure out how get the changed file: ```js compiler.plugin('invalid', (filename) => { console.log('File changed', filename); }); ``` Now that I know how...

I'm seeing this and other errors as well. It's the only module in my project with errors in TypeScript 4.1. ```ts node_modules/jodit/src/core/helpers/checker/is-imp-interface.ts:17:2 - error TS2322: Type 'unknown' is not assignable...

Blocked by #584

Hi @xdan, thanks for addressing the original errors, but it seems like the new code has issues as well: ```bash tsc: node_modules/jodit/src/types/view.d.ts:107:2 - error TS2502: 'options' is referenced directly or...

I changed them locally from `this[...` to the type, such as `T`, and TypeScript got farther, but stopped after finding more errors: ```bash tsc: node_modules/jodit/src/core/plugin-system.ts:82:46 - error TS2339: Property 'extraPlugins'...

This warning is typically for the a third party dependency or dependency of a dependency getting installed. It's not likely useful for developer running the install. This is made extra...

I created a package that does this https://github.com/dylang/source-map-diff

Can you run grunt with `grunt -v` to get verbose output and paste your output here? BTW - if you use `^` npm will install the newest version that is...

Thanks, good find, I guess I didn't realize what I was doing back then! Do you want to make a pull request to fix these?