Closed Jule- closed 2 years ago
@3cp is this still relevant?
This works on latest skeleton. It's probably some default change between gulp v3 and v4.
If having trouble with symlink with latest skeleton, try gulp.src's options follow: true
.
https://gulpjs.com/docs/en/api/src#options
The gulp.src option can be edited in various files in aurelia_project/tasks/
whenever gulp.src is used.
Oh, it works on macOS where symlink is true symlink. No sure about windows, I guess symlink is simulated on the platform which causes many trouble. (My knowledge might be wrongly based outdated file system in windows)
@3cp thank you
I'm submitting a bug report
Please tell us about your environment:
Operating System: OSX 10.13|Windows 10
Node Version: 6.9.2
NPM Version: 3.10.9
Browser: all
Language: ESNext
Loader/bundler: RequireJS
Current behavior: Following this kind of project hierarchy:
And assuming that each
main.js
have animport Class from './shared_sources/class';
, when I try to build withau build
I have some errors due to symlinks. If I pastclass.js
in a standard folder all goes fine.Error:
What is the expected behavior? I expect that aurelia-cli build system can follow symlinks correctly.
What is the motivation / use case for changing the behavior? Sometimes you want to share some source code between two aurelia project because they use the same models for example and you don't want to make a new repository for that. And you don't want to add in your developpement process to change your library, commit, push, then npm/yarn again in each of your subprojects in order to test your changes.