updating to node ES6See original GitHub issue
So, not sure if this is a desired goal or not but…
Consumption of SlickGrid in a modern project that is driven by
npm and built via webpack/babel/ES6 can be a pain in the backside, given the reliance on globals, order of loading, lack of implicit dependencies.
I got annoyed and took out the bits from the repo one by one and added them to a new repo, converting in the process.
It’s WIP - https://github.com/DimitarChristoff/slickgrid-es6 - but it occurs to me, it can probably be done as a fork of this instead of a fresh standalone effort. If this sort of direction is something of interest, ping me and we can convert and do stuff as a pull request and an actual fork of 6pac/SlickGrid.
TL;DR; took your repo, made it work with node/ES6, removed IE8, moved to jquery 3.1.0, all deps are npm, works fine in React or whatever.
- Created 7 years ago
- Comments:11 (4 by maintainers)
Top GitHub Comments
you can use UMD and set build target to that but it can be annoying when deps like jquery-ui are completely non compliant and need special requirejs configurations to get going.
On Tuesday, 23 August 2016, Ben McIntyre firstname.lastname@example.org wrote:
@ZheyangSong we have had a few requests for various package managers, which I’m working through. I’m not personally that keen on AMD, and it would have an impact on the codebase making it harder to use for non-AMD projects. The changes in the repo you mention are pretty clear and simple and fall in a single commit. I’d suggest turning them into a patch and then applying that patch to this repo or the repo of your choosing. Hey presto! an AMD compliant branch! I suppose I could do this on a branch of my repo, but it’s just ‘1 more thing’ ™. But seriously, I’d be maintaining about 10 separate branches if I did this for everyone who asked. You are free to fork this repo, add AMD and keep it up to date. I’m happy to point people at that in my wiki.