In an answer on SO, it's said that absoluteRuntime (setting it to true) in @babel/transform-runtime should be used when authoring a library.

Library: If you are authoring a library, use only @babel/transform-runtime with corejs option plus @babel/runtime-corejs3 as dependency, and @babel/preset-env for syntax transpilation with useBuiltIns: false. Also I would transpile packages I would use from node_modules. For this you will need to set the absoluteRuntime option (https://babeljs.io/docs/en/babel-plugin-transform-runtime#absoluteruntime) to resolve the runtime dependency from a single place, because @babel/transform-runtime imports from @babel/runtime-corejs3 directly, but that only works if @babel/runtime-corejs3 is in the node_modules of the file that is being compiled.

However, absoluteRuntime: true will effectively produce all imports into absolute paths pointing to a place on my local computer like this:

import _slicedToArray from "/Users/myself/project/node_modules/@babel/runtime/helpers/builtin/es6/slicedToArray";
import _createClass from "/Users/myself/project/node_modules/@babel/runtime/helpers/builtin/es6/createClass";
import _inherits from "/Users/myself/project/node_modules/@babel/runtime/helpers/builtin/es6/inherits";

If I was authoring a library, wouldn't pointing the imports to a local absolute path mean the library will only work on my computer and not anywhere else when imported into other projects on a different computer?

What is the rationale behind doing this and why is building local absolute paths a good thing for libraries when it is supposed to be distributed but will only work on my own computer? Is there something else I need to do to my library when using absoluteRuntime?