-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Node Catalogues & NPM configuration file for Devices #3588
Node Catalogues & NPM configuration file for Devices #3588
Comments
npmrc files and catalogue.json are already included in the settings pushed to a device that is bound to an Instance. So does this only apply to Application bound instances?
|
Correction, .npmrc file and catalogue.json are added if they are contained in a snapshot. The only way to get them into a snapshot is currently if the snapshot comes from an Instance where they have been configured. |
We need to decide what should take priority here. Should a device be allowed to set it's own .npmrc file that overrides the one in the snapshot? |
Yes
Yes in Dev Mode |
See #2802 a potential follow-up item |
That will prove very difficult. Devices would need to be restarted for this to take effect. |
Which isn't a big deal since #3292 right? It should be now more or less like for an hosted instance |
Verified in pre-staging instance |
Epic
#3172
Description
As a FlowFuse user who works with devices,
I want to be able to configure the .npmrc file and Node Catalogues within FlowFuse,
So that I have the flexibility to include my own external npm modules and integrate the Auth Dashboard plugin seamlessly into my development environment.
Which customers would this be availble to
Team + Enterprise Tiers (EE)
Acceptance Criteria
No response
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
The text was updated successfully, but these errors were encountered: