cfware/babel-plugin-bare-import-rewrite

Babel plugin to rewrite bare imports for use on web browsers.

babel-plugin-bare-import-rewrite's Issues

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.6.4 to 7.7.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ✅ Tidelift: Dependencies checked (Details).
• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.6.2 to 7.6.3.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.8.7 to 7.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[Feature request] fail when import cannot be resolved

Currently when an import cannot be resolved an error is logged but compilation does not fail. This makes it hard to spot errors during development, as code will be broken but it's not very apparent why.

Especially if you are working in the browser, and not looking at the terminal, the message: Failed to resolve module specifier "foo". Relative references must start with either "/", "./", or "../". is not very helpful.

I suggest adding an option to allow failing when a module could not be resolved.

I can work on a PR for this.

An in-range update of babel7 is breaking the build 🚨

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.1.1 to 7.1.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Create option for `preserveSymlinks`.

This should be passed on to resolve. From the resolve readme for current releases:

• opts.preserveSymlinks - if true, doesn't resolve basedir to real path before resolving.
  This is the way Node resolves dependencies when executed with the --preserve-symlinks flag.
  Note: this property is currently true by default but it will be changed to
  false in the next major version because Node's resolution algorithm does not preserve symlinks by default.

So maybe babel-plugin-bare-import-rewrite should set preserveSymlinks: false by default and list this a breaking change. master of resolve already has preserveSymlinks: false by default but no releases have been made from master.

Requirements:

• testing strategy to ensure the functionality is well defined and works as expected
• determine what this does/should do in Windows or if it's a noop (specifically junctions)

[Feature request] Skip absolute path imports

Currently, if I have a /src/some-folder/my-component.js file like that:

import { html } from '@polymer/polymer/polymer-element.js'
import { MyProjectDependency } from '/src/my-project-dependency.js'
...

The URL rewrite transforms that to:

import { html } from '/node_modules/@polymer/polymer/polymer-element.js'
import { MyProjectDependency } from '/src/my-project-dependency.js'
...

And it outputs the following warning:

 Could not resolve '/src/my-project-dependency.js' in file '...../src/some-folder/my-component.js'.

---

Would it be possible to rewrite the absolute paths to relative paths like the polymer-build project does?

An in-range update of resolve is breaking the build 🚨

The dependency resolve was updated from 1.15.0 to 1.15.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

resolve is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

---

Commits

The new version differs by 4 commits.

• c1750d6 v1.15.1
• 5e1f5c8 [Dev Deps] update @ljharb/eslint-config
• 891bd89 [Fix] correct behavior when requiring . with same name (#212)
• 16c1170 [Tests] allow node 5 on windows to fail due to npm registry bug

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.8.7 to 7.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

An in-range update of babel7 is breaking the build 🚨

---

☝️ Important announcement: Greenkeeper will be saying goodbye 👋 and passing the torch to Snyk on June 3rd, 2020! Find out how to migrate to Snyk and more at greenkeeper.io

---

There have been updates to the babel7 monorepo:

• • The devDependency @babel/core was updated from 7.8.7 to 7.9.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

This monorepo update includes releases of one or more dependencies which all belong to the babel7 group definition.

babel7 is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

• ❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

---

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

Invoke visitors in Program exit

This is a request to move the path traversal for CallExpression/Import/Export/etc. to the Program exit. I have a sample repo to load a React application in ESM and use this module to apply the import path resolution.

The problem is that my CJS->ESM plugin must run first, and then this plugin. Since Babel doesn't have a way to properly schedule tasks, the fix here would be to run later.

module.exports = ({types: t}) => ({
	inherits: syntax.default,
	visitor: {
		Program: {
			exit(path, { opts }) {
				path.traverse({
					CallExpression(path) {

I can open a PR to show the change as well.

[Feature request] multiple module directories

At work we are migrating from bower to npm, where some dependencies will be in bower_components and others in node_modules.

Would you mind if we make modulesDir an array of component directories to search in? The polymer tools also allowed this.

I can work on a PR for this.