-
-
Notifications
You must be signed in to change notification settings - Fork 255
Added support for npm:[email protected] #975
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for looking into this. Does jspm install npm:bootstrap
not work at all otherwise? What errors are you getting? Is there an issue anywhere for this at all?
{ | ||
"main": "js/bootstrap", | ||
"directories": { | ||
"lib": "dist" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a breaking change, do we really need this. It can be better to use dist/js/bootstrap
etc in the other configurations.
"shim": { | ||
"js/bootstrap": { | ||
"deps": [ | ||
"jquery", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Invalid trailing comma.
"exports": "$" | ||
} | ||
}, | ||
"files": [ "dist" ] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Best to leave this out as well, no reason to filter out the other files if users may find them useful.
"lib": "dist" | ||
}, | ||
"shim": { | ||
"js/bootstrap": { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
js/bootstrap
-> dist/js/bootstrap
.
So I see 2 choices:
What would be the preference? |
On
So don't we just need to be setting the |
That's weird, my output is different. (see below)
|
Try removing any local overrides first? |
(from the package.json) |
And that's exactly why I'd discourage files and directories.lib. |
There are no local overrides. Totally fresh installs, npm & jspm. |
Actually that is exactly right. The published package configuration for Bootstrap contains the following: "jspm": {
"main": "js/bootstrap",
"shim": {
"js/bootstrap": {
"deps": "jquery",
"exports": "$"
}
},
"files": [
"css",
"fonts",
"js"
]
}, The files filter here is thus what is restricting things. I would suggest trying If that works out, and seems the right fix, then we can add the override and also get the change into bootstrap itself. |
Furthermore, |
@peebeebee adding extra files is not a breaking change, only removing them is, so I'd be happy to add this into the registry here. I'm open to a similar PR for |
Now npm:bootstrap includes the dist folder, not the source files