Fix astro add with third-party integrations

[natemoo-re]

Changes

Previously, running astro add astro-pkg, would generate weird code:

import { defineConfig } from 'astro/config';
import astro from 'astro-pkg';

export const defineConfig({
  integrations: [
    astro()
  ]
})

With this PR, the generated code will now be:

import { defineConfig } from 'astro/config';
import pkg from 'astro-pkg';

export const defineConfig({
  integrations: [
    pkg()
  ]
})

Testing

Nah, we don't test astro add

Docs

N/A

[changeset-bot]

🦋 Changeset detected

Latest commit: f4ac4a1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 13 packages

Name	Type
astro	Patch
@e2e/astro-component	Patch
@e2e/error-react-spectrum	Patch
@e2e/error-sass	Patch
@e2e/errors	Patch
@e2e/lit-component	Patch
@e2e/preact-component	Patch
@e2e/react-component	Patch
@e2e/solid-component	Patch
@e2e/solid-recurse	Patch
@e2e/svelte-component	Patch
@e2e/e2e-tailwindcss	Patch
@e2e/ts-resolution	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[bholmesdev]

Good catch! Will note it's a side effect of bad dash handling. So for a package called astro-long-pkg-name, it'll generate long() instead of longPkgName(). Might be worth a more sustainable fix?

[natemoo-re]

That's a good point, this was a lazy fix. I'll do what you're suggesting ☺️

[bholmesdev]

I am forever in your idebt

[FredKSchott]

now that we're post v1.0 I'm feeling the burn to start adding some tests to anything like this that we missed for v1.0, but okay to keep kicking this can a bit longer until we're out of the release bug swarm

[bholmesdev]

@FredKSchott +1! I vote using Vitest for this for snapshot testing though. The lack of snapshots in create-astro made for a tough test authoring experience and brittle tests we ended up removing.

[FredKSchott]

LGTM! Merging so that we can get this into the next release