You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 4, 2021. It is now read-only.
You can configure this plugin to disregard external packages that don't have a pkg.module property, but what you're really doing when you do that is excluding non-ES2015 packages.
But that fails when it's a deep import:
import{print}from'graphql/language/printer';
The plugin happily resolves this path, not considering what type of file it is. And that can cause problems. I propose we add an option to specifically exclude non-ES2015 modules, using the unambiguous grammar proposal. Maybe something like this:
plugins: [resolve({modulesOnly: true// would also automatically set `module: true, jsnext: true`})]
You can configure this plugin to disregard external packages that don't have a
pkg.module
property, but what you're really doing when you do that is excluding non-ES2015 packages.But that fails when it's a deep import:
The plugin happily resolves this path, not considering what type of file it is. And that can cause problems. I propose we add an option to specifically exclude non-ES2015 modules, using the unambiguous grammar proposal. Maybe something like this:
Any thoughts?
Ref Rich-Harris/packd#2 (#90 is part of that, but we'd still need this).
The text was updated successfully, but these errors were encountered: