Skip to content

V8Js 3.0.0 #525

Open
2 of 4 issues completed
Open

Description

@redbullmarky

Hey
It's probably time to consider creating a new release, as we're a little behind despite having added some little features and fixes since these:

Release: Version 2.1.1 (June 19)
Tag: Version 2.1.2 (Aug 20)

I'll start collecting some of the things changed since, so the notes & docs can be updated etc.

Quoted from #526 (comment) :

I think what we have to do at least is

apart from that, maybe someone want's to work on the lib/include file lookup, there's some frustration coming up here and there, that it should be different, see #522. Possibly also add/update some notes in the README

Activity

  1. dinamic commented on Jun 11, 2024

    @dinamic

    The major selling point for the new tag would be the PHP 8 support.

    The current version in PECL is 2.1.2 and it does not play well with PHP 8.

    configure:5825: checking for V8 version
    configure:5855: g++ -o conftest -g -O2  -I/usr/local/include -std=c++11  -L/usr/local/lib conftest.cpp -lstdc++   -lv8_libplatform -Wl,-rpath,/usr/local/lib -L/usr/local/lib -lv8  >&5
    In file included from /usr/include/node/v8-local-handle.h:12,
                     from /usr/include/node/v8-array-buffer.h:12,
                     from /usr/include/node/v8.h:24,
                     from conftest.cpp:10:
    /usr/include/node/v8-internal.h: In function 'void v8::internal::PerformCastCheck(T*)':
    /usr/include/node/v8-internal.h:646:38: error: 'remove_cv_t' is not a member of 'std'; did you mean 'remove_cv'?
      646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
          |                                      ^~~~~~~~~~~
          |                                      remove_cv
    /usr/include/node/v8-internal.h:646:38: error: 'remove_cv_t' is not a member of 'std'; did you mean 'remove_cv'?
      646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
          |                                      ^~~~~~~~~~~
          |                                      remove_cv
    /usr/include/node/v8-internal.h:646:50: error: template argument 2 is invalid
      646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
          |                                                  ^
    /usr/include/node/v8-internal.h:646:63: error: '::Perform' has not been declared
      646 |             !std::is_same<Data, std::remove_cv_t<T>>::value>::Perform(data);
          |                                                               ^~~~~~~
    configure:5855: $? = 1
    configure: program exited with status 1
    configure: failed program was:
    | /* confdefs.h */
    | #define PACKAGE_NAME ""
    | #define PACKAGE_TARNAME ""
    | #define PACKAGE_VERSION ""
    | #define PACKAGE_STRING ""
    | #define PACKAGE_BUGREPORT ""
    | #define PACKAGE_URL ""
    | #define PHP_V8_EXEC_PATH "/usr/local/lib/libv8.so"
    | /* end confdefs.h.  */
    | #include <v8.h>
    | #include <iostream>
    | #include <fstream>
    | using namespace std;
    |
    | int main ()
    | {
    | 	ofstream testfile ("conftestval");
    | 	if (testfile.is_open()) {
    | 		testfile << v8::V8::GetVersion();
    | 		testfile << "\n";
    | 		testfile.close();
    | 		return 0;
    | 	}
    | 	return 1;
    | }
    configure:5867: result: NONE
    configure:5894: error: could not determine libv8 version
    
  2. redbullmarky commented on Nov 18, 2025

    @redbullmarky
    CollaboratorAuthor

    why has there been no news about it?

    Time is often the case with many people. Keeping on top of things as the V8 library its compiled against gets new updates, etc.
    I haven’t had a look over things myself for a little while but if there was someone else that’s had recent success building against latest V8 and/or even the one that’s bundled with node, I’d be keen to try and get things updated a bit with a bit of a steer.
    Then I guess it’d be down to @stesie to give it the thumbs up for 3.0

  3. added theissue type on Apr 2, 2026
  4. removed theissue type on Apr 2, 2026
  5. added theissue type on Apr 2, 2026
  6. self-assigned this
    on Apr 20, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions