dependencies that reference more than one directory level of traversal (../) in their ESM specifiers do not resolve correctly

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

As part of working on a project, came across a Stencil generated WC that had references to a dependency that did an export of sibling files like so

export {
  ...
} from '../client/index.js';

This tracks as we only check for ./ in our code 🤫

Details

In addition to this support, I also found cases where I would specifically need to check for a "barrel" / index.js file at a directory for bare imports like this?

import { BUILD, NAMESPACE } from '@stencil/core/internal/app-data';