Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 1 addition & 5 deletions projects/private-app-getting-started-template/package.json
Original file line number Diff line number Diff line change
@@ -1,11 +1,7 @@
{
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I wonder if it would it be beneficial to remove this file entirely? Running npm install at the wrong directory level seemed to be a pretty common support issue, and the post install was mitigating this in at least some of the cases. Are there benefits to keeping this file around without the scripts block?

Copy link
Contributor Author

@banderson banderson Aug 15, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I could not agree more, @joe-yeager! I took a baby step to remove the fangs from this issue with this small change, but I am also happy if we go all the way and remove it!

"name": "hubspot-get-started-project",
"private": true,
"version": "0.1.0",
"description": "Basic example of a UI Extension built with HubSpot's React developer tools",
"scripts": {
"postinstall": "cd ./src/app/extensions/ && npm install && cd ../app.functions && npm install",
"build": "npm run build --prefix ./src/app/extensions/"
},
"author": "HubSpot",
"license": "MIT"
}