Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[es-dev-server] imports with a . are not resolved

See original GitHub issue

As a performance optimization we don’t resolve imports to files with a .. However this is not correct in all cases, some files may contain a . and the user might not including the actual file extension. We may need to let go of this optimization.

Issue Analytics

State:
Created 4 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

bashmishcommented, Aug 27, 2019

@LarsDenBakker if I understood correctly, maybe keep the optimisation for .js which will cover 99% of cases?

0reactions

LarsDenBakkercommented, Aug 27, 2019

Actually, we already have an array of file extensions we want to resolve to (default .mjs and .js). We can just use that array.

Top Results From Across the Web

open-wc/es-dev-server - GitHub

The --node-resolve flag resolves this bare import to the actual file path before serving it to the browser: import foo from './node_modules/bar/bar.js';.

Developing Without a Build (2): es-dev-server

This will rewrite imports in your modules using NodeJS module resolution before serving them to the browser. To see how this works let's...

es-dev-server - npm

The import maps proposal aims to resolve the need for editing your source code before it is served to the browser but it...

Web Dev Server - Modern Web

Efficient browser caching for fast reloads · Transform code on older browsers for compatibility · Resolve bare module imports for use in the...

es-dev-server-rollup - npm Package Health Analysis - Snyk

Security Policy: No. We found a way for you to contribute to the project! Looks like es-dev-server-rollup is missing a security policy.