Troubles migrating away from bower

@johnnyicon wrote:

I’ve been having issues with migrating away from bower using bower-away. When I try to start my project now, I get the following error:

yarn start 
yarn run v1.12.3
$ ember serve

Directory not found: bower_components


Stack Trace and Error Report: /var/folders/8h/j9zgv6t52pz2qd_xsnhlv0yr0000gn/T/error.dump.e8be45d71975e1facda7f232149d57d3.log
error Command failed with exit code 1.

In case there are those who don’t know how bower-away works, it adds all the dependencies in bower.json to the "dependencies" section of package.json with a prefix: "@bower_components/<package_name>": "<package_url>". It then replaces the physical bower_components directory with a symlink to node_modules/@bower_components.

Looking at the strack trace, the source code that is throwing the error (Line 261) seems to not like symlinks…

# node_modules/broccoli/lib/builder.js

254    checkInputPathsExist() {
255      // We might consider checking this.unwatchedPaths as well.
256      for (let i = 0; i < this.watchedPaths.length; i++) {
257        let isDirectory;
258        try {
259          isDirectory = fs.statSync(this.watchedPaths[i]).isDirectory();
260        } catch (err) {
261          throw new this.constructor.BuilderError('Directory not found: ' + this.watchedPaths[i]);
262        }
263        if (!isDirectory) {
264          throw new this.constructor.BuilderError('Not a directory: ' + this.watchedPaths[i]);
265        }
266      }
267    }

Any ideas? Or is there a more reliable away to migrate away from bower?

Thanks in advance!

Posts: 1

Participants: 1

Read full topic