[Feature Request] Browser compatible version

[HHogg]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

👋 It would be really helpful to have a browser compatible version. Do you think there is an approach to supporting this? For example either by inserting the invalid core module names at build time (the build of this library), or shipping a separate browser version just without the core module validation?

[MarketingPip]

I have also requested this. I would like to create a PR that solves this. Perhaps if browser based - you need to bring the built ins yourself? (As you mentioned) I think would be best approach. We could possibly fetch dynamically directly from node js repo based on version or set default?

[manferlo81]

Maybe allow the user to pass the built-in modules, that is the only reason why it doesn't work in the browser, well... apart from the fact the there is no require in the browser. But if the user passes the built-in modules you no longer need to use require...

validate-npm-package-name/lib/index.js

Line 2 in 208b9f4

const { builtinModules: builtins } = require('module')

validate-npm-package-name/lib/index.js

Lines 55 to 57 in 208b9f4

	if (builtins.includes(name.toLowerCase())) {
	warnings.push(name + ' is a core module name')
	}

...or just simply have a browser version without the built-in module name validation.

...or maybe something like...

// because typeof if safe even if it doesn't exist
const builtins = typeof require === 'undefined' ? [] : require('module').builtinModules;

...but UMHO allowing the user to control the built-in module names is the way to go.