-
Notifications
You must be signed in to change notification settings - Fork 574
Open
Description
Sorry if I'm naive and ignorant here. I'm trying to get started with setup in my dev machine following instructions here. I can't start the server because BASEHUB_TOKEN is missing. I gave a placeholder as BASEHUB_TOKEN="bshb_pk_xxxx"
but still getting lot of errors like:
⨯ ./packages/cms/components/feed.tsx:1:1
Export Pump doesn't exist in target module
> 1 | export { Pump as Feed } from 'basehub/react-pump';
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2 |
The export Pump was not found in module [project]/node_modules/basehub/react-pump.js [app-rsc] (ecmascript).
The module has no exports at all.
All exports of the module are statically known (It doesn't have dynamic exports). So it's known statically that the requested export doesn't exist.
./apps/web/app/[locale]/layout.tsx:2:1
Export Toolbar doesn't exist in target module
1 | import './styles.css';
> 2 | import { Toolbar as CMSToolbar } from '@repo/cms/components/toolbar';
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
3 | import { DesignSystemProvider } from '@repo/design-system';
4 | import { fonts } from '@repo/design-system/lib/fonts';
5 | import { cn } from '@repo/design-system/lib/utils';
The export Toolbar was not found in module [project]/node_modules/basehub/next-toolbar.js [app-rsc] (ecmascript).
The module has no exports at all.
All exports of the module are statically known (It doesn't have dynamic exports). So it's known statically that the requested export doesn't exist.
./packages/cms/components/toolbar.tsx:1:1
Export Toolbar doesn't exist in target module
> 1 | export { Toolbar } from 'basehub/next-toolbar';
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2 |
I don't need a CMS, can't we make it optional instead of making it mandatory?
JarvisPrestidge and waynelinks
Metadata
Metadata
Assignees
Labels
No labels