Page MenuHomePhorge

Add package.json for aphlict
ClosedPublic

Authored by deadalnix on Jun 19 2021, 17:15.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Mar 27, 02:04
Unknown Object (File)
Mon, Mar 25, 23:32
Unknown Object (File)
Mon, Mar 25, 16:19
Unknown Object (File)
Sun, Mar 24, 05:19
Unknown Object (File)
Wed, Mar 20, 09:39
Unknown Object (File)
Fri, Mar 15, 03:52
Unknown Object (File)
Wed, Mar 13, 16:14
Unknown Object (File)
Thu, Mar 7, 18:29

Details

Summary

This makes the whole setup easier, future proof and reproducible.

Test Plan
cd support/aphlict/server/
npm install

See that ws gets installed as expected.

Diff Detail

Repository
rP Phorge
Branch
aphlictnpm
Lint
Lint Warnings
SeverityLocationCodeMessage
Warningsupport/aphlict/server/package-lock.json:10TXT3Line Too Long
Unit
No Test Coverage
Build Status
Buildable 15
Build 15: arc lint + arc unit

Event Timeline

My only concern here is that technically this introduces issues for any user install that already contains an untracked package support/aphlict/server/package-lock.json

I feel that this needs to be addressed in "release notes" or "upgrade notes" somewhere - However, we do not yet have this process defined?

This was handled by Phacility/Phabricator with their changelog and process for promoting stable

My only concern here is that technically this introduces issues for any user install that already contains an untracked package support/aphlict/server/package-lock.json

I feel that this needs to be addressed in "release notes" or "upgrade notes" somewhere - However, we do not yet have this process defined?

This was handled by Phacility/Phabricator with their changelog and process for promoting stable

In my updates to the Diviner documentation (T15012), I’ve been referencing a change log like Phacility had. We should probably continue to use that, at the very least.

My only concern here is that technically this introduces issues for any user install that already contains an untracked package support/aphlict/server/package-lock.json

I feel that this needs to be addressed in "release notes" or "upgrade notes" somewhere - However, we do not yet have this process defined?

This was handled by Phacility/Phabricator with their changelog and process for promoting stable

I'm happy to add a release note somewhere, I'm just not sure where. Could you point me to the appropriate place?

I'm happy to add a release note somewhere, I'm just not sure where. Could you point me to the appropriate place?

We don't have one - I started T15014 to discuss

We should probably exclude the package-lock.json from linting rules, because it is auto generated.

This revision is now accepted and ready to land.Jun 20 2021, 21:43

I'm going to land this one as to not wait on things that are not sorted out, with the obvious note that a release note would be advantageous.

This revision was landed with ongoing or failed builds.Jun 21 2021, 10:46
This revision was automatically updated to reflect the committed changes.