Failed to resolve module specifier "process". Relative references must start with either "/", "./", or "../".

[zababurinsv]

I create module and exclude

import * as $i5RZ6$process from "process";
import * as $i5RZ6$buffer from "buffer";
import * as $i5RZ6$events from "events";
import {inherits as $i5RZ6$inherits, TextEncoder as $i5RZ6$TextEncoder, TextDecoder as $i5RZ6$TextDecoder, inspect as $i5RZ6$inspect, format as $i5RZ6$format} from "util";
import {strictEqual as $i5RZ6$strictEqual} from "assert";
import {Transform as $i5RZ6$Transform} from "stream";
import {StringDecoder as $i5RZ6$StringDecoder} from "string_decoder";
import * as $i5RZ6$path from "path";

In previous versions, I made a module and ran it in the browser. Now I can't do it because of these imports.

Parcel 2.5.0

  "targets": {
    "module": {
      "includeNodeModules": true,
      "optimize": false,
      "isLibrary": true,
      "sourceMap": false,
      "source": "./src/index.module.mjs",
      "distDir": "./modules",
      "outputFormat": "esmodule",
      "publicUrl": "/",
      "scopeHoist": true
    }
  },

[mischnic]

Are you trying to build a webapp to run in the browser?

Then don't call the target "module". Specifically, don't set "isLibrary": true

[mischnic]

Could you try to determine where $i5RZ6$path is used in the generated file?

[zababurinsv]

path.posix

  const manifest = Object.assign({
    name: name,
    type: type,
    accessController: (path.posix || path).join('/ipfs', accessControllerAddress)
  },

[zababurinsv]

 for (const i in migrationKeys) {
    try {// @ts-ignore
      const key = path.join(keyRoot, migrationKeys[i])
      const val = await oldCache.get(migrationKeys[i])
      if (val) await options.cache.set(key, val)
    } catch (e) {
      logger.debug(e.message)
    }
  }

[mischnic]

But I've just tried to use your config and compile this:

import path from "path";

console.log(path.join("abc"));

export function Foo() {
	return <div>asd</div>;
}

And with both Parcel 2.0.0 and 2.5.0, there's an import to "path" in the output.

[zababurinsv]

It's a mystery to me how I made modules before.

How can I generate a module without imports?

If I disable isLibrary it will make the file without export.

If it doesn't work out, unfortunately you'll have to use webpack.

How was this conclusion made before?

function $parcel$interopDefault(a) {
  return a && a.__esModule ? a.default : a;
}
function $parcel$export(e, n, v, s) {
  Object.defineProperty(e, n, {get: v, set: s, enumerable: true, configurable: true});
}
var $parcel$global =
typeof globalThis !== 'undefined'
  ? globalThis
  : typeof self !== 'undefined'
  ? self
  : typeof window !== 'undefined'
  ? window
  : typeof global !== 'undefined'
  ? global
  : {};
  


export {$0c390372e548812a$export$2e2bcd8739ae039 as default};

[damian-pastorini]

2023 this is still an issue.
I'm trying to use parcel to export a lib that checks for both "process" and "window" to define the current "context", the problem is:
parcel will add as first line on the generated dist file something like this:

import * as $2KqY6$process from "process";`

that leads to:

Uncaught TypeError: Failed to resolve module specifier "process". Relative references must start with either "/", "./", or "../".

In the browser.

Some possible fixes (on our side):

• Make parcel avoid generate the import for "process" but I still don't know how. I'm looking into "exclude" or something like that.
• Try to replace the "process" import by an empty object var process={}; to avoid all the issues.

[damian-pastorini]

More into: https://parceljs.org/features/dependency-resolution/#package-entries

Parcel checks the following fields (in order):

source – If the module is behind a symlink (e.g. in a monorepo, or via npm link), then Parcel uses the source field to compile the module from source. The source field can also be used as an alias mapping if a package has multiple entry points – see Aliases below for details.
exports – Package exports, see below for details.
browser – A browser-specific version of a package. If building for a browser environment, the browser field overrides other fields. The browser field can also be used as an alias mapping if a package has multiple entry points – see Aliases below for details.
module – An ES module version of the package.

So basically, that doesn't seems to be the case, because browser comes before module in our package and Parcel does it the other way around, maybe that is the bug?