Skip to content

Publish Next packages #6

Open
Open
@eric-burel

Description

@eric-burel

Building packages meant specifically for Next is specific.
We probably don't need to have a full build process, and we should instead let Next do it's magic as much as possible, directly within the Next user app.
Exactly like a Meteor package does not necessarily need a lot of transpiling to be published.

See this discussion for example, regarding process.env in NPM packages: vercel/next.js#17262

I did a test with next-transpile-modules but did not manage to make it work as expected yet: martpie/next-transpile-modules#120

At the moment, Next packages specific to vulcan are shipped directly with the starter, they are not real NPM packages.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions