Thanks Ben! Last time when we upgraded to 5.3, we used gcc 4.8 on Linux, VS 2015 on Windows to compile v8 and our own product. Do we need to use a higher version of compiler this time?
On Monday, June 4, 2018 at 1:09:33 AM UTC-7, Ben Noordhuis wrote: > > On Mon, Jun 4, 2018 at 2:36 AM, Jane Chen <jxch...@gmail.com <javascript:>> > wrote: > > I am making plans to upgrade v8 for our next major release. We are > > currently running 5.3. It looks like that the current stable release is > > 6.7. Is this a good version to upgrade to? Is the module API ready to > be > > used? Any significant incompatibilities from version 5.3 that we should > be > > aware of? > > > > Thanks a log in advance. > > Node.js is currently at V8 6.6 and plans to upgrade to 6.7 in the near > future. You'll need to implement the module loader yourself (V8 > provides just the hooks) but otherwise modules work. > > The only big backwards incompatible change I can think is the > replacement of the old debugger with the V8 inspector, everything else > is relatively minor. I guesstimate upgrading is a few hours of work > if you don't care about debugging, maybe a day or two if you do. > -- -- v8-users mailing list v8-users@googlegroups.com http://groups.google.com/group/v8-users --- You received this message because you are subscribed to the Google Groups "v8-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to v8-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
