Skip to content

Missing plugin dependencies #57

Open
@mantidfly

Description

@mantidfly

Not sure about the policy in this matter, but I've found one inconsistency while trying to run the project.

When I spinned up this project on netlify from the github repo, everything works fine out of the box. It worked both for manual installation (creating repo first and then importing to netflify) and the direct start from the templates.

The problem occured when I tried to run the same project from the bitbucket repo. I couldn't find any explicit error, but the page hasn't been deployed correctly. Deploy was successful with cypress errors and page was not found when visiting the production url.

After digging up I've finally realised that when you spin up the project from github, netlify detects that this is a next.js app and applies the @netlify/plugin-nextjs plugin under the hood (it's visible in the UI plugins section). In case of bitbucket I had to do that step manually within the UI or add config section:

[[plugins]]
  package = "@netlify/plugin-nextjs"

along with adding proper dev dependency to package.json.

If this plugin is required to correctly run the app in the netlify, maybe it's better to add it to the config, to avoid inconsistencies across multiple git providers? Alternatively netlify plugin that autodetects the project's framework could be improved, but IMHO explicit dependencies seems to be cleaner and allow to avoid similar issues in the future.

Thanks for the starter anyway. It's really helpful! :)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions