Analytics Node Next #3967
Analytics Node Next #3967
Conversation
|
hi @silesky, here's a draft of the docs for the Analytics Node Next changes that we discussed before the holidays. Could you please take a look and input any comments or note other changes that need to be made? Thank you! |
| redirect_from: '/connections/sources/catalog/libraries/server/node-js/quickstart/' | ||
| strat: node-js | ||
| --- | ||
|
|
||
| > warning "Deprecation of Analytics Node.js Classic" | ||
| > On [date], Segment will end support for Analytics Node.js Classic, which includes versions [1.x.x] and older. Upgrade to Analytics Node.js 2.0. See the [Analytics Node.js 2.0] docs to learn more. |
There was a problem hiding this comment.
I lean towards saying that the "deprecation" date is 4/1/2023 (the end of Q1). cc @chrisradek @tlalfano
I created a story https://segment.atlassian.net/browse/LIBWEB-1309
| --- | ||
|
|
||
| Our Node.js library lets you record analytics data from your node code. The requests hit our servers, and then we route your data to any destinations you have enabled. | ||
| > warning "Deprecation of Analytics Node.js Classic" | ||
| > On [date], Segment will end support for Analytics Node.js Classic, which includes versions [1.x.x] and older. Upgrade to the new version of Analytics Node.js. See the updated [Analytics Node.js] docs to learn more. |
There was a problem hiding this comment.
@silesky what's the current version number of the classic version?
There was a problem hiding this comment.
6.2.0
seen: https://www.npmjs.com/package/analytics-node?activeTab=versions
This detail about versions is not really needed IMO, as we are deprecating one entire package in favor of a new package, so we are starting over on a new package who's first non beta version will be 1.0 (currently at 0.1-beta.9).
Old package: analytics-node (to be deprecated)
New package: @segment/analytics-node
✅ Deploy Preview for segment-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Looks good!
I found a few instances of absolute links to docs pages, like here for example.
src/connections/sources/catalog/libraries/server/node/migration.md
Outdated
Show resolved
Hide resolved
src/connections/sources/catalog/libraries/server/node/migration.md
Outdated
Show resolved
Hide resolved
src/connections/sources/catalog/libraries/server/node/classic.md
Outdated
Show resolved
Hide resolved
src/connections/sources/catalog/libraries/server/node/classic.md
Outdated
Show resolved
Hide resolved
|
|
||
|
|
||
| ## Plugin architecture | ||
| When you develop against [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/), the plugins you write can augment functionality, enrich data, and control the flow and delivery of events. From modifying event payloads to changing analytics functionality, plugins help to speed up the process of getting things done. |
There was a problem hiding this comment.
Dumb question...but I assume this just means that Node plugins are bound by the same constraints as A.js?
There was a problem hiding this comment.
@silesky can you confirm? ^ I'm not sure if they're bound by the same constraints
There was a problem hiding this comment.
This paragraph LGTM.
Yes, they share the same plugin pipeline code so they should have feature parity.
I might be able to answer this question better if you gave me an example of what you mean by constraints, but I'm pretty ok with the text as is FWIW
Co-authored-by: markzegarelli <[email protected]>
src/connections/sources/catalog/libraries/server/node/migration.md
Outdated
Show resolved
Hide resolved
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Proposed changes
Merge timing
Related issues (optional)