Check that JSPM 0.17 works as expected?

[kevcjones-archived]

Need to verify that the behaviour will work as expected when running with JSPM 0.17....

[KarlPurk]

The following warning was given when installing plugin-scss using JSPM 0.17.0-beta.12

warn Package github:KevCJones/plugin-scss@0.2.5 has a directories.lib override
     configuration which will work, but is deprecated for directories.dist in future
     jspm versions.

[kevcjones-archived]

Good to know, will look at options next week

[kevcjones-archived]

This branch is a WIP
I had to flatten the the new jspm.browser.js into a single jspm.config for now. Its not clear to me yet how to change the builder setup. Seems i need both parts as one? Or a 3rd parameter.

[KarlPurk]

The following error is given when trying to bundle a project using the new jspm bundle x --watch command.

 [plugin-scss]  Stacklite :: github:KevCJones/plugin-scss/sass-inject-build.js -> npm:sass.js
 [plugin-scss]  Error: File to import not found or unreadable: jspm:styles/colors
       Parent style sheet: stdin
        on line 1 of stdin
>> @import "jspm:styles/colors";
   ^

[kevcjones-archived]

For now remove the JSPM:: and explicitly import using relative URLs. Until we work out the finer qualities of the new builder and config setup the old package helpers don't seem to be respected. I vaguely recall reading a release note by Guy about this for short handing your .JS files. Perhaps this extended to other package shorthand too. More explicitness everywhere is my observation so far.