npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

domain-wait

v1.3.0

Published

Allows you to use async/await syntax in ASP.NET Core NodeServices prerendering. Also includes some features.

Downloads

762

Readme

npm version npm downloads

Description

domain-wait - is a library that allows you to use async/await syntax in ASP.NET Core NodeServices prerendering.

Changes

v. 1.2.0 (2019-05-05)
  • Important! Breaking changes. See the installation manual for migration.
  • Stability and critical fixes.
v. 1.1.1 (2019-04-08)
  • Fixed library for Linux support.
v. 1.1.0 (2018-07-11)
  • Added new feature which prevent calling for isomorphic fetch requests twice (in server prerendering and after it - on client side).

Installation

  • NPM
npm install domain-wait
  • Add following lines to the SSR's entry point JS-file:

// 1. Import library.
import { connect, getCompletedTasks } from "domain-wait";

//...

// 2. Find this function (it's a NodeServices entry point).
export default createServerRenderer((params) => {
    
    //...

    // 3. Find the promise.
    return new Promise<RenderResult>((resolve, reject) => {        

        //...

        connect(params); // 4. Add in this line before (!) the first call of the render function.

        renderApp(); // First call of the render application function.

        //...     
        
        resolve({
            //...
            globals: {
                //...
                completedTasks: getCompletedTasks() // 5. Add this line to the each (!) 'globals' object.
                //...
            }
            //...
        });

    });
})
  • Add variable to the window object Add the completedTasks array to the window object in Razor's .cshtml file:
@*Instead of using "aspnet-prerender" attribute / tag helper*@
@inject Microsoft.AspNetCore.SpaServices.Prerendering.ISpaPrerenderer
@{
    var prerenderResult = await prerenderer.RenderToString(%Path to JS file which will be entry point for the SSR%, customDataParameter: %Your data object from ASP.NET Core%);
    var completedTasksJson = prerenderResult?.Globals?["completedTasks"]?.ToString();
}

<head>
    <script>
    window.completedTasks = @Html.Raw(completedTasksJson)
    </script>
</head>

<body>
    @*Instead of using "aspnet-prerender" attribute / tag helper*@
    <div id="app">@Html.Raw(prerenderResult?.Html)</div>
</body>

Usage

  • Import library
import { wait, transformUrl } from "domain-wait";
  • Tell to the NodeServices to wait for asynchronous function. Example with Axios:
// NodeServices will be waiting for the request with Axios async method.
await wait(async (transformUrl) => {
    var url = transformUrl("/api/Person");
    var result = await Axios.get(url);	
    // ...
});

License

MIT