next dev with purs?

[jamesdbrock]

The package.json created by this template looks like this.

  "scripts": {
    "dev": "next dev",
    "build": "npm run build:spago && npm run build:next",
    "build:spago": "spago build",
    "build:next": "next build",

So I can build the project in one step: npm run build.

But when I run npm run dev, the next.js watcher doesn't rebuild my .purs files when necessary. Is there a way to configure next dev to rebuild the .purs files?

[sigma-andex]

If you are using VSCode then the purs ide server should automatically build the purs files and next should pick up the changes. Maybe try restarting the purs ide server in vscode?
Otherwise you could do something like

"dev": "next dev && spago build -w",

but if the ide server works properly this shouldn't be necessary..

[jamesdbrock]

If you are using VSCode then the purs ide server should automatically build the purs files and next should pick up the changes

I do use VSCode and I’ve noticed that sometimes the next dev watcher does pick up the PureScript changes, but mostly it doesn’t work. I think maybe there is a race condition somewhere in here.

1. I save Page.purs.
2. PureScript IDE detects the change to Page.purs, compiles to output/.
3. next dev detects the change to output/, compiles “client and server.”

[jamesdbrock]

When next dev compiles “client and server” it looks like this.

wait  - compiling...
event - compiled client and server successfully in 458 ms (882 modules)
warn  - Fast Refresh had to perform a full reload. Read more: https://nextjs.org/docs/messages/fast-refresh-reload

[sigma-andex]

• I save Page.purs.

• PureScript IDE detects the change to Page.purs, compiles to output/.

• next dev detects the change to output/, compiles “client and server.”

This should be fine as it is a change. I just checked and in my .next.config.js I also have the folllowing:

/** @type {import('next').NextConfig} */
const nextConfig = {
  reactStrictMode: true, // Recommended for the `pages` directory, default in `app`.
  experimental: {
    appDir: true,
  },
  webpack: (config, options) => {
    config.resolve.modules.push("output");

    config.snapshot = {
      ...(config.snapshot ?? {}),
      // Add all node_modules but @next module to managedPaths
      // Allows for hot refresh of changes to @next module
      managedPaths: [/^(.+?[\\/]node_modules[\\/])(?!@next)/],
    };
    return config;
  },
};

Maybe this is missing

[jamesdbrock]

Maybe this is missing

Yeah, that seems to refresh more reliably, thanks!