It's fast and easy, and you can get in contact with others straight away...

Enter a Display Name
Enter your full name or a display name. Businesses, couples and families are also accepted. e.g.
Model Trains Inc.,
Sam and Janis Allen
Enter a username
Your username must be at least 6 characters in length, contain both letters and numbers and end in a number, but can not contain spaces or other characters.
Suggested usernames:
Password strength:
Your password can be up 250 characters in length and can contain letters, numbers, punctuation marks and spaces.
Hint: a secure password is long but easy to remember and not complex, e.g.
Jules Verne is an excellent author
Retype password
Enter the same password again to check for errors.

By signing up you agree to our Terms of Use & Privacy Policy

Drag and zoom to move the image.
Note: Only JPG files are currently accepted.
Address 2
Post Code
View As
Sort by
Cancel esc
Click for advanced permissions.
Content Suitability
Show Replies As
Sort Replies By ·
  Paste Link Undo Redo ctrl enter
    The Minimum Viable Product explained

    An MVP ‘satisfies early customers’This first instance of your product must be good enough to solve the problem for your customers — they should get value out of it from day one. Your MVP must be usable and effective so users engage with it and potentially pay for it.
    Your early customers should be so happy with your product to act as promoters — to recommend it to others and publicly share their satisfaction (if not excitement).
      Renaming N-API to Node-API
      The reason for this blog post is to explain what motivated us to rename N-API to Node-API. The issue that is tracking the transition was:
      You may have noticed N-API changed to Node-API in the documentation within the Node.js project. N-API has always stood for Node-API but was often pronounced NAPI. A concern was raised, that when pronounced that way, it could be mistaken for a derogatory term. We therefore made it our goal to clarify that N-API is Node-API whenever possible without introducing breaking changes.
      What’s changing (only in more recent versions):
      References: Documentation, blog posts, and similar will now refer to “Node-API”.
      Folders: Internally referenced folders (eg. test folders) have been renamed from n-api to node-api.
      Badges hosted on Node repositories: Existing badges’ image contents have been updated to “Node-API” without changing their URLs.
      New symbols: Additions to Node-API and related projects will now have a different prefix, eg. node_api_get_module_file_name.
      Types, macros, and defines: Externally-facing API names, such as features guards, will now start with NODE_API_ instead of NAPI_
      New node arguments: Node-API configuration via node command line arguments, eg.- -force-node-api-uncaught-exceptions-policy, will refer to the new name.
      What’s not changing:
      Old symbols: Existing symbols (eg. napi_create_reference) will remain the same. This ensures ABI stability, such that a previously compiled add-on will continue to load in newer Node versions.
      Types, macros and defines: Names like napi_status, NAPI_MODULE, the Napi namespace (in node-addon-api) will remain the same. This ensures existing code can be recompiled with no changes.
      We believe that we’ve made this change in a way that addresses the issue while limiting the impact to users of Node-API and hope this post helps you understand the approach and what to look out for. As always if you have any questions/concerns please open an issue in or
        Why is Vue the best?

        Now why Vue.js and not any other framework? Is it because more and more tech giants are trending towards it or are there any reasons for real? Let’s find out!
        The satisfaction ratio of Vue.js is incredibly higher among all frameworks.
        It’s very easy to integrate the Vue.js into any pre-existing application by adding a layer of pages or visual elements.
        A component-based and featured packed framework is necessary to build an application with a chance to modify it in the future. And Vue.js is just the right one to have in your tech stack as it’s in-built support libraries allow flexibility to build an application with scalability in the future.
        The interesting advantage of this framework is one must only have a basic understanding of HTML, CSS, and Javascript and then you can learn Vue.js framework to build an application very effortlessly.
        Having DevTools, now debugging an application is super easy with the Vue.js framework.
        Along with the ease of use, its ability to integrate, flexibility, and scalability make it very convenient to utilize it for any application development project.
        The component-based method of the Vue.js framework gives good manageability over the entire project and no re-writable work is required in the future.
        All data can be stored without rendering or modifications and can be availed whenever you want.


        Loading messages...
        ( )
        Content Suitability
        Click for advanced permissions.

        Attach an image or file

        Cancel esc