To Repeat.... CSV files are industry standard files. There are NO default values for field size.
But in SQL Server all columns must have a size. No matter if CSV files are a standard are not. Yes, the import wizard could default to nvarchar(MAX), but that is bad for a couple of more reasons. So the table has nothing to do with the industry standard. And it is something you have to create. The tool may be nice and *try* to create it for you, but it needs to create the table before it reads the file.
Then again, we have no idea if the columns size was the problem, since you have not cared to share an error message or given us any details of what you wanted to do.
This is a technical forum to get help with SQL Server. It's not a place where you do if all you want to do is to express your frustration.