Skip to Main Content
Customer Feedback

We love feedback from you on our products and the problems in your daily work that you would like us to solve. Please describe the challenge you're encountering and your desired outcome. Be as detailed as possible.

For technical issues or bugs please head to Support or our Developer Community. You can assign up to 10 votes in total. Thank you for your feedback.

Status explanation: 'Future Consideration' = Continuing to collect further feedback, not planned at this time. 'Investigating' = Prioritized for deeper customer and feasibility investigations ahead of planning development.

Status Investigating
Categories CMS, Spire & Mobius
Created by Guest
Created on Sep 1, 2022

Spire: Use package.json to allow 3rd party node modules in projects

When Spire first launched there was a mechanism to add a package.json file to the root of a blueprint’s directory and that would get picked up in the build and install any node modules from it. It didn’t work as it was supposed to and therefore was disabled with the plan to re-enable it after the initial Spire development was feature complete and stable.

Now that Spire is at a pretty good spot, we would like to request that this be re-implemented/re-added back into the solution.

  • Guest
    Reply
    |
    Nov 9, 2022

    Thanks Sara!

  • Optimizely
    Sara Winter
    Reply
    |
    Nov 9, 2022

    Thank you for submitting this request! Our team is currently investigating if and how we may implement this feature, particularly with consideration of our wide client base. We will update this ticket once we have completed this investigation.