Bradley Farias

@ljharb ah, `file:///app/node_modules/sql/` in the example above then; by default it wouldn't resolve using the result of the current data in policies and a new data point would be needed...

@ljharb I do not believe it recursively searches for a package containing "exports" I believe given our documentation it stops on the first package boundary not for a module located...

Maybe I misunderstood the last comment since the resolver wouldn't be recursing up to find the source of a deep import's package boundary with this API but instead resolving the...

@ljharb the nearest package boundary stops at the first package.json (recursing parent directories) but "exports" check is only during node_modules traversal (only recurses to find the module by a name)....

that seems fine, my complaint is we don't define a "package root" currently. as @giltayar points out you can have multiple package boundaries: ``` /app /app/node_modules/logger/package.json - package boundary at...

CC: @nodejs/modules

@jkrems you do not need to be an IETF member to provide feedback

@mcollina it is just a comment period, if you endorse it personally or through the TSC it doesn't matter, the editors are mostly just looking for some signal of +/-...

please put feedback on the official IETF mailing list, the editors won't be reading stuff on this issue

I think so (this is all new to me)