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
I haven't tried 0.17 just yet, do all linked packages sit within jspm_packages/local folder? Currently, I'm filtering out jspm_packages modules, but I'm thinking of adding a flag or a setting to specify jspm packages watch exclusion mask. It's done for performance reasons, so we don't have chokidar watching thousands of files which are unlikely to change, only with jspm config change (which will trigger full rebuild).
So with the new linking system, it creates a symlink. If you do the following:
jspm link ~/path/to/project it will read the package.json, and add a symlink in the local folder with that name to the path supplied. Pretty straight forward, and it's a good way to work on packages that aren't yet published to npm.
However, if you supply an npm/github path afterwards, it symlinks over the project in the npm or github folder. So if I was using jspm-watch in my jspm project:
jspm link ~/js/jspm-watch npm:jspm-watch would symlink the ~/js/jspm-watch folder as jspm_packages/npm/[email protected]
As for performance, it so far seems to be running on the lowest common denominator quite well, a 6-7 year old thinkpad. Still, it would be nice to be more specific.
This was something I really wanted personally, as it helps flow. I managed to make it work really simply by just using the same chokidar internals:
This is only a working solution for jspm 0.17 of course.
The text was updated successfully, but these errors were encountered: