Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Skeleton CLI Beta - Public Feedback #3134

Open
endigo9740 opened this issue Jan 20, 2025 · 3 comments
Open

Skeleton CLI Beta - Public Feedback #3134

endigo9740 opened this issue Jan 20, 2025 · 3 comments
Assignees
Labels
administration Items related to the project but outside the code. enhancement New feature or request
Milestone

Comments

@endigo9740
Copy link
Contributor

endigo9740 commented Jan 20, 2025

View the the close beta ticket here.

Known Issues

(See the Sub-issues list)

Found an Issue?

Report it using the comment section below.

@endigo9740 endigo9740 added this to the v3.0 (Next) milestone Jan 20, 2025
@endigo9740 endigo9740 pinned this issue Jan 20, 2025
@endigo9740 endigo9740 mentioned this issue Jan 20, 2025
17 tasks
@endigo9740 endigo9740 added enhancement New feature or request administration Items related to the project but outside the code. labels Jan 20, 2025
@nullpointerexceptionkek
Copy link
Contributor

The CLI runs npm install after everything.
However, the logs are not streamed to the CLI.

This can make the CLI seem to be "stucked"

@nullpointerexceptionkek
Copy link
Contributor

It would also be very helpful if the CLI would generate a file or logs in which specific files contain components that are not transferable.

Current behavior is that the CLI will silently remove the import while leaving the components there, resulting in import errors

@endigo9740
Copy link
Contributor Author

endigo9740 commented Jan 24, 2025

Current behavior is that the CLI will silently remove the import while leaving the components there, resulting in import errors

Just FYI this is an intentional design choice.

  • Removing the imports is not trivial, but possible.
  • Removing the implementation in the templates would be a huge mess; lots of ways for this to go wrong.

We're trying to remove everything we can within reason, so that end users have a few less things to juggle. Errors will be triggered in the project regardless of whether the import remains or not. And errors in this case can help point you towards the files and components that need attention.

I have no qualms with duplicating this in the log as well. But one way or the other users will have to address the component remnants. That can't be helped unfortunately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
administration Items related to the project but outside the code. enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants