You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to avoid as much as possible a full-fledged monorepo, because they are simply hard to setup. But maybe I am wrong, pnpm workspaces are worth investigating.
Anyway for a first version I am trying to stick with file imports. "shared" is simply a code folder, but outside of the actual app because it's used by multiple app. The "shared/package.json" is just there for development, the main app must make sure that it also includes the right dependencies, because only its package.json will be actually used during build/run.
The only other alternative is to make the Next.js app "fat" and keep scripts there, a bit like Meteor used to work.
Use cases
move the normalization script to a "scripts" folder (currently in Next surveyform)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Idea:
I need to dig the experimental "externalDir" of Next.js:
I'd like to avoid as much as possible a full-fledged monorepo, because they are simply hard to setup. But maybe I am wrong, pnpm workspaces are worth investigating.
Anyway for a first version I am trying to stick with file imports. "shared" is simply a code folder, but outside of the actual app because it's used by multiple app. The "shared/package.json" is just there for development, the main app must make sure that it also includes the right dependencies, because only its package.json will be actually used during build/run.
The only other alternative is to make the Next.js app "fat" and keep scripts there, a bit like Meteor used to work.
Use cases
Resources