Snowpack 2.9.0 breaks codewith process.cwd is not a function. Works fine in 2.8.0

[benoitg]

With Snowpack 2.8.0 everything works fine.

The problem occurs in VFile (https://github.com/vfile/vfile), part of unified

Here is a chunk of the traceback in our specific project if trying to run with snowpack 2.9.0

Uncaught TypeError: process.cwd is not a function
    at new VFile (remark.js:215)
    at VFile (remark.js:209)
    at Function.processSync (remark.js:758)
    at markdownToReact (feedback-markdown.js:84)

Ultimately, it chokes on this line: https://github.com/vfile/vfile/blob/9a2b75531a125fe46a05127f3f804dc86123fbf0/core.js#L55

Once again, in 2.8.0 everything works fine. In 2.9.0, the code chokes in the exact same way when using either:

• the same configuration
• using the new --polyfill-node

My (working in 2.8.0) snowpack.config.js is:

module.exports = {
  scripts: {
    "mount:public": "mount public --to /",
    "mount:src": "mount src --to /_dist_",
  },
  plugins: ['@snowpack/plugin-babel', "@snowpack/plugin-dotenv"],
  devOptions: {},
  buildOptions: {sourceMaps: false},
  installOptions: {
    sourceMap: false,
    rollup: {
      plugins: [require("rollup-plugin-node-polyfills")()],
    },
  },
};

I presume this is related to #854

[FredKSchott]

This is a good followup for #854 - how far do we go in polyfilling process? I think we could just take the Rollup polyfill in its entirety (https://github.com/ionic-team/rollup-plugin-node-polyfills/blob/master/polyfills/process-es6.js), so that we keep parity and also don't have to keep addressing one offs like this one.

Creating a prioritized issue to track.

[gr2m]

@benoitg can you please check if the problem is resolved with the latest snowpack release? It was resolved in #920 and released in https://github.com/pikapkg/snowpack/releases/tag/snowpack%402.9.1

[benoitg]

It did (I confirmed on the bug, but forgot to confirm here, sorry).